all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: MON KEY <monkey@sandpframing.com>
Cc: 6283@debbugs.gnu.org
Subject: bug#6283: doc/lispref/searching.texi reference to octal code `0377'	correct?
Date: Wed, 02 Jun 2010 20:46:41 +0300	[thread overview]
Message-ID: <83y6exs4xq.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTiljuo5cZsmHG4dw2J6wZ5-xtE2CFHCPjNAt1FqO@mail.gmail.com>

> Date: Wed, 2 Jun 2010 12:06:34 -0400
> From: MON KEY <monkey@sandpframing.com>
> Cc: 
> 
> On Tue, Jun 1, 2010 at 2:26 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Do you not see a contradiction of convention here?
> >
> > No, I see two different conventions used interchangeably.
> 
> Do you recognize that one convention is explicity recognized by
> Emacs/Emacs-elisp whereas the other is not?

Yes, but I don't think that the manual should use only forms that can
be evaluated or read by the Lisp reader.  A manual is intended for
human consumption (except where it shows examples of code), not for
the Lisp reader.

> Can you maybe see how the interchangeable use of these two different
> conventions might be confusing to the audience for which the _elisp_
> manual was intended

No, I don't see how using conventions widely accepted in the
programming world should be confusing to Lisp programmers.  I actually
think that readers who are not too experienced in Emacs Lisp will find
this text easier to understand if it uses conventions they are
familiar with and used to.

Anyway, I think it's time to end this discussion.  It's quite clear we
disagree on this issue, and no repetition of the same arguments will
change that.  Thanks for taking time to make your position clear.





      parent reply	other threads:[~2010-06-02 17:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 17:28 bug#6283: doc/lispref/searching.texi reference to octal code `0377' correct? MON KEY
2010-05-27 18:10 ` Eli Zaretskii
2010-05-27 22:59   ` MON KEY
2010-05-29 14:28     ` Kevin Rodgers
     [not found]   ` <AANLkTikjCByug1U69tbhsnmS4c1VXSNzoqAOAxmbt3bI@mail.gmail.com>
2010-05-28  7:15     ` Eli Zaretskii
2010-05-28 23:20       ` MON KEY
2010-05-29  6:45         ` Eli Zaretskii
2010-05-31  5:35           ` MON KEY
2010-05-31 18:49             ` Eli Zaretskii
2010-06-01  0:24               ` MON KEY
2010-06-01 18:38                 ` Eli Zaretskii
2010-06-02 19:41                   ` MON KEY
2010-06-03 14:39                     ` Kevin Rodgers
2010-05-31 14:45           ` MON KEY
2010-05-31 18:51             ` Eli Zaretskii
2010-05-31 23:44 ` MON KEY
2010-06-02 16:06 ` MON KEY
2010-06-02 17:30   ` Chong Yidong
2010-06-02 17:46   ` Eli Zaretskii [this message]

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=83y6exs4xq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=6283@debbugs.gnu.org \
    --cc=monkey@sandpframing.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.