From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: make-variable-buffer-local change
Date: Sat, 26 Sep 2009 12:10:08 +0300 [thread overview]
Message-ID: <8363b6t6kv.fsf@gnu.org> (raw)
In-Reply-To: <E6D1D2C2A88C4368945EFC048B07C7E0@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <lekktu@gmail.com>, <dann@ics.uci.edu>, <lennart.borgman@gmail.com>,
> <emacs-devel@gnu.org>
> Date: Fri, 25 Sep 2009 13:10:51 -0700
>
> > > > I'd say "use" covers both kinds of use, but I'll defer to natives.
> > >
> > > It's not a question of native speakers. "Use" here refers
> > > to what the string is _for_; what it is used for.
> >
> > Would replacing "use" with "set" solve this problem?
>
> You missed the point. We don't want to talk about places where the value is set.
> What's important is what the variable is for.
The doc string already includes that information:
String to display in buffer listings for buffers not visiting a file.
If you think this is insufficient or can suggest a better wording,
please do. But you began this sub-thread by complaining against the
next sentence, which, at least for me, caused confusion as to what you
were complaining about.
> What is important is to let users know that they can set it for use by
> buffer-listing code.
I agree, and I think the above portion of the doc string does
precisely that.
next prev parent reply other threads:[~2009-09-26 9:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 16:09 make-variable-buffer-local change Dan Nicolaescu
2009-09-25 16:32 ` Juanma Barranquero
2009-09-25 16:50 ` Lennart Borgman
2009-09-25 16:57 ` Juanma Barranquero
2009-09-25 17:35 ` Drew Adams
2009-09-25 17:41 ` Juanma Barranquero
2009-09-25 18:06 ` Drew Adams
2009-09-25 19:09 ` Eli Zaretskii
2009-09-25 20:10 ` Drew Adams
2009-09-26 9:10 ` Eli Zaretskii [this message]
2009-09-25 21:04 ` Stefan Monnier
2009-09-25 22:10 ` Drew Adams
2009-09-26 1:30 ` Stefan Monnier
2009-09-26 1:42 ` Juanma Barranquero
2009-09-26 9:03 ` Eli Zaretskii
2009-09-25 17:07 ` Dan Nicolaescu
2009-09-25 17:31 ` Juanma Barranquero
2009-09-25 19:46 ` Dan Nicolaescu
2009-09-25 20:16 ` Juanma Barranquero
2009-09-25 20:51 ` Dan Nicolaescu
2009-09-25 21:21 ` Juanma Barranquero
2009-09-25 21:13 ` Tom Tromey
2009-09-25 19:49 ` Stefan Monnier
2009-09-25 21:07 ` Stefan Monnier
2009-09-25 21:25 ` Dan Nicolaescu
2009-09-25 21:44 ` Tom Tromey
2009-09-25 19:50 ` Stefan Monnier
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=8363b6t6kv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.