unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Tom Tromey <tromey@redhat.com>
Cc: emacs-devel@gnu.org
Subject: Re: Updated project-specific settings patch
Date: Tue, 20 May 2008 10:02:28 -0400	[thread overview]
Message-ID: <87wslpkr9n.fsf@stupidchicken.com> (raw)
In-Reply-To: <m3fxseufgl.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon,  19 May 2008 15:55:06 -0600")

Tom Tromey <tromey@redhat.com> writes:

>>>>>> "Chong" == Chong Yidong <cyd@stupidchicken.com> writes:
>
> Chong> Could you also write a patch for the Emacs manual?  (It doesn't have to
> Chong> be ready before you check in the code, but the sooner the better.)
>
> The patch included a change to doc/emacs/custom.texi.

I missed that part of your patch.  Sorry for the noise.  I've read it
now, and have a couple of minor comments.

  Emacs provides a way to specify local variable values per-directory.
  This can be done one of two ways.

This is confusingly worded: is there "a way" or "two ways"?  I suggest
changing this to:

  Directory variables are file-local variables that apply to all the
  files within a directory.  You can define directory variables in two
  ways.

Also,

  Unsafe directory-local variables are handled in the same way as
  unsafe file-local variables.

You need to be more specific about what happens when the user tries to
define unsafe directory-local variables.


On another note: does your patch include a enable-directory-variables
option, analogous to enable-local-variables, that allows the user to
turn off directory variable scanning?  If not, maybe should.




  reply	other threads:[~2008-05-20 14:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 17:07 Updated project-specific settings patch Tom Tromey
2008-05-19 18:51 ` Stefan Monnier
2008-05-19 18:55   ` Miles Bader
2008-05-19 19:00     ` Tom Tromey
2008-05-20  2:35       ` Miles Bader
2008-05-19 19:23   ` Tom Tromey
2008-05-19 19:51     ` Re[2]: Project local variables & EDE (was: Updated project-specific settings patch) Eric M. Ludlam
2008-05-19 22:41     ` Updated project-specific settings patch Michael Olson
2008-05-20  0:04       ` Stefan Monnier
2008-05-20  3:18         ` Michael Olson
2008-05-20  0:14       ` Miles Bader
2008-05-20  7:19         ` David Kastrup
2008-05-19 20:29   ` David Kastrup
2008-05-19 21:57     ` Stefan Monnier
2008-05-19 19:32 ` joakim
2008-05-19 20:11   ` Re[2]: " Eric M. Ludlam
2008-05-20  3:27     ` Eli Zaretskii
2008-05-19 20:02 ` Chong Yidong
2008-05-19 21:55   ` Tom Tromey
2008-05-20 14:02     ` Chong Yidong [this message]
2008-05-20 18:45       ` Stefan Monnier
2008-05-21  0:04         ` Miles Bader
2008-05-21 19:49       ` Tom Tromey
2008-05-22  3:46         ` Chong Yidong
2008-05-23  6:31           ` Michael Olson

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wslpkr9n.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=tromey@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).