all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 7777@debbugs.gnu.org
Subject: bug#7777: 24.0.50; incompatible change for `directory-abbrev-alist' not in NEWS
Date: Sun, 09 Jan 2011 06:02:00 +0200	[thread overview]
Message-ID: <83pqs6k9mv.fsf@gnu.org> (raw)
In-Reply-To: <87d3o7kqb8.fsf@stupidchicken.com>

> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: "'Eli Zaretskii'" <eliz@gnu.org>, 7777@debbugs.gnu.org
> Date: Sat, 08 Jan 2011 17:01:47 -0500
> 
> "Drew Adams" <drew.adams@oracle.com> writes:
> 
> > The other part of this bug is the location of the manual entry: Why
> > the Elisp manual?  This is a user option.  If we feel it is important
> > to tell users about this in a manual, why wouldn't the Emacs manual be
> > the right one?
> 
> Sounds reasonable; I've done as suggested (and added the anchoring
> explanation).

Didn't you like the change I did (on the emacs-23 branch) in the doc
string?  You also threw away the text I added to the ELisp manual, to
explain this.  Was it wrong or unclear?





  parent reply	other threads:[~2011-01-09  4:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 19:49 bug#7777: 24.0.50; incompatible change for `directory-abbrev-alist' not in NEWS Drew Adams
2011-01-03 20:04 ` Andreas Schwab
2011-01-03 21:44   ` Drew Adams
2011-01-03 20:24 ` Eli Zaretskii
2011-01-03 21:44   ` Drew Adams
2011-01-04  4:01     ` Eli Zaretskii
2011-01-04  4:12       ` Drew Adams
2011-01-07 16:01         ` Eli Zaretskii
2011-01-08 22:01         ` Chong Yidong
2011-01-08 22:35           ` Drew Adams
2011-01-09  4:02           ` Eli Zaretskii [this message]
2011-01-13  5:21             ` Chong Yidong
2011-01-28 17:31               ` Chong Yidong
2011-01-03 21:46   ` Sean Sieger

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=83pqs6k9mv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=7777@debbugs.gnu.org \
    --cc=cyd@stupidchicken.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.