shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-25 01:34:28 +03:00
Code
5ada98cdc7
systemd/.dir-locals.el

29 lines
1.2 KiB
EmacsLisp
Raw Normal View History

Keep emacs configuration in one configuration file. On 07.03.2011 19:04, Lennart Poettering wrote: > > Oh, I had assumed that .vimrc trick would allow project-wide vim > modelines without having to edit each and every single file. > > Currently, every file does contain an emacs modeline at the top. It > would be fair I guess to add a vim modeline to all those files too, even > though it's not necessarily pretty. Hi, maybe it makes sense to go in the opposite direction: add .dir-locals.el in the top directory. The settings are actually identical in all .[ch] files.
2011-03-07 21:23:04 +03:00
; Sets emacs variables based on mode.
; A list of (major-mode . ((var1 . value1) (var2 . value2)))
; Mode can be nil, which gives default values.
coding style: reduce text width to 109 characters Patches are shown on github with a fixed width (no matter how wide the window is). When line numbers are high (we have some files with 5 digit line numbers), the diff does not fit, and horizontal scrolling must be used when viewing the patch. This is super annoying. Let's reduce the width a bit. I think 109 is still very wide, but at least the github issue should be alleviated.
2018-12-06 17:45:19 +03:00
; Note that we set a line width of 109 for .c and XML files, but for everything
editors: only extend line width to 119 for C and XML files For all other files leave the line width at 79 as before. This is a good idea since we generally don't want text files such as catalog files, unit files or README/NEWS files to be line-broken at 119 since they are regularly browsed on text terminals. While we are at it, also add a couple of comments to the various files. (Note that .editorconfig doesn't carry line-width information, simply because the specification doesn't know the concept.)
2016-02-10 14:27:35 +03:00
; else (such as journal catalog files, unit files, README files) we stick to a
; more conservative 79 characters.
; NOTE: If you update this file make sure to update .vimrc and .editorconfig,
; too.
coding style: reduce text width to 109 characters Patches are shown on github with a fixed width (no matter how wide the window is). When line numbers are high (we have some files with 5 digit line numbers), the diff does not fit, and horizontal scrolling must be used when viewing the patch. This is super annoying. Let's reduce the width a bit. I think 109 is still very wide, but at least the github issue should be alleviated.
2018-12-06 17:45:19 +03:00
((c-mode . ((fill-column . 109)
editors: only extend line width to 119 for C and XML files For all other files leave the line width at 79 as before. This is a good idea since we generally don't want text files such as catalog files, unit files or README/NEWS files to be line-broken at 119 since they are regularly browsed on text terminals. While we are at it, also add a couple of comments to the various files. (Note that .editorconfig doesn't carry line-width information, simply because the specification doesn't know the concept.)
2016-02-10 14:27:35 +03:00
(c-basic-offset . 8)
editors: specify fill column Let's be a bit more precise with the editor configuration and specify a higher fill column of 119. This isn't as emacs' default of 70, but also not particularly high on today's screens. While we are at it, also set a couple of other emacs C coding style variables.
2016-01-08 02:24:06 +03:00
(eval . (c-set-offset 'substatement-open 0))
(eval . (c-set-offset 'statement-case-open 0))
(eval . (c-set-offset 'case-label 0))
(eval . (c-set-offset 'arglist-intro '++))
Better C code formatting of arguments in Emacs In [PR#11696][1] it came up that the formatting of continued arguments should follow the default Emacs style. To ensure this happens when someone has changed his setting in her private config, the value should be set by *dir-locals.el*. [1]: https://github.com/systemd/systemd/pull/11696#pullrequestreview-205463987
2019-02-28 17:53:40 +03:00
(eval . (c-set-offset 'arglist-close 0))
(eval . (c-set-offset 'arglist-cont-nonempty '(c-lineup-gcc-asm-reg c-lineup-arglist)))))
editors: only extend line width to 119 for C and XML files For all other files leave the line width at 79 as before. This is a good idea since we generally don't want text files such as catalog files, unit files or README/NEWS files to be line-broken at 119 since they are regularly browsed on text terminals. While we are at it, also add a couple of comments to the various files. (Note that .editorconfig doesn't carry line-width information, simply because the specification doesn't know the concept.)
2016-02-10 14:27:35 +03:00
(nxml-mode . ((nxml-child-indent . 2)
coding style: reduce text width to 109 characters Patches are shown on github with a fixed width (no matter how wide the window is). When line numbers are high (we have some files with 5 digit line numbers), the diff does not fit, and horizontal scrolling must be used when viewing the patch. This is super annoying. Let's reduce the width a bit. I think 109 is still very wide, but at least the github issue should be alleviated.
2018-12-06 17:45:19 +03:00
(fill-column . 109)))
meson: also indent scripts with 8 spaces
2017-04-25 02:40:02 +03:00
(meson-mode . ((meson-indent-basic . 8)))
scripts: use 4 space indentation We had all kinds of indentation: 2 sp, 3 sp, 4 sp, 8 sp, and mixed. 4 sp was the most common, in particular the majority of scripts under test/ used that. Let's standarize on 4 sp, because many commandlines are long and there's a lot of nesting, and with 8sp indentation less stuff fits. 4 sp also seems to be the default indentation, so this will make it less likely that people will mess up if they don't load the editor config. (I think people often use vi, and vi has no support to load project-wide configuration automatically. We distribute a .vimrc file, but it is not loaded by default, and even the instructions in it seem to discourage its use for security reasons.) Also remove the few vim config lines that were left. We should either have them on all files, or none. Also remove some strange stuff like '#!/bin/env bash', yikes.
2019-04-04 15:10:42 +03:00
(sh-mode . ((sh-basic-offset . 4)
(sh-indentation . 4)))
make dir-locals work again with emacs 26.1 After upgrading to emacs-26.1-1.fc28.x86_64 I noticed that our .dir-locals.el files weren't honoured anymore (specifically the fill column variable is not correctly set for c-mode files). I finally tracked this down to the order in which items are listed in .dir-locals.el: if the "nil" one is listed last everything works, otherwise, it's the one that is applied instead of the c-mode one. This patch simply swaps the entries, and puts the "nil" one last. My emacs lisp fu is a bit too limited to understand the full impact for this, and why emacs 26.1 changed behaviour in this regard, but from an outsider's view the order shouldn't negatively affect things otherwise, hence this patch.
2018-06-20 11:59:44 +03:00
(awk-mode . ((c-basic-offset . 8)))
(nil . ((indent-tabs-mode . nil)
(tab-width . 8)
(fill-column . 79))) )
Copy Permalink