From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: andrew.burgess@embecosm.com, gdb-patches@sourceware.org
Subject: Re: [PATCHv2] gdbserver: Add .dir-locals.el file
Date: Mon, 02 Mar 2020 19:19:00 -0000 [thread overview]
Message-ID: <83imjmy37t.fsf@gnu.org> (raw)
In-Reply-To: <752d5ea0-4c7b-ca63-e1f3-b03364c53a7f@redhat.com> (message from Pedro Alves on Mon, 2 Mar 2020 18:12:53 +0000)
> Cc: andrew.burgess@embecosm.com, gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Mon, 2 Mar 2020 18:12:53 +0000
>
> > Put a single file in the parent directory of those 3, I think.
>
> Good point. This would affect all projects in the top level,
> though perhaps the file is right for all of them.
You can arrange for the settings to affect only some of the
subdirectories, the Emacs manual shows an example of that.
> OOC, if we wanted to say, source "../gdb/.dir-locals.el" from
> a gdbserver/.dir-locals.el file, would it be possible?
.dir-locals.el supports 'eval' forms, so you could in principle do
anything there. But my advice is to stick to simplicity, for reasons
of speed of visiting files, if nothing else. Also, maintaining such a
tricky file would need an Emacs expert, something that is not
guaranteed (although currently we have several on board).
> I guess a symlink would do too. Except that might not work
> as nicely on Windows filesystems.
IME, symlinks in versioned directories are a PITA.
next prev parent reply other threads:[~2020-03-02 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 9:53 [PATCH] " Andrew Burgess
2020-03-02 10:17 ` Aktemur, Tankut Baris
2020-03-02 12:31 ` [PATCHv2] " Andrew Burgess
2020-03-02 14:06 ` Pedro Alves
2020-03-02 17:08 ` Andrew Burgess
2020-03-02 17:34 ` Pedro Alves
2020-03-02 17:58 ` Eli Zaretskii
2020-03-02 18:13 ` Pedro Alves
2020-03-02 19:19 ` Eli Zaretskii [this message]
[not found] ` <20200305151232.GB3317@embecosm.com>
2020-03-05 15:26 ` Eli Zaretskii
2020-03-05 16:00 ` Pedro Alves
[not found] ` <BYAPR11MB3030342645BFA8E7610CF862C4E70@BYAPR11MB3030.namprd11.prod.outlook.com>
2020-03-02 12:02 ` [PATCH] " Andrew Burgess
2020-03-02 14:05 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83imjmy37t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox