Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Issues
  • #610

Closed
Open
Created Oct 05, 2020 by gsell@gsellOwner

define and set project wide editor variables

For the time being we set local editor variables by appending something like the following lines to source code files:

// vi: set et ts=4 sw=4 sts=4:
// Local Variables:
// mode:c++
// indent-tabs-mode: nil
// require-final-newline: nil
// End:

This approach is extremely inflexible. For a single change of an editor variable all files must be changed.

Emacs provides project wide settings via a file named .dir-locals.el in the top-level directory. This mechanism also supports multiple modes, e.g. for C, C++ and CMake files.

Vim supports a similar mechanism via a plugin each user can install in his ~/.vim/pack directory.

Instead of appending local variable settings to each file, project-wide configuration files should be used.

Edited Oct 05, 2020 by snuverink_j
Assignee
Assign to
OPAL 2021.1
Milestone
OPAL 2021.1 (Past due)
Assign milestone
Time tracking