unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: Documentation of transient-mark-mode is sloppy, wrong, and confused.
Date: Fri, 29 May 2009 13:17:36 +0000	[thread overview]
Message-ID: <20090529131736.GF2793@muc.de> (raw)
In-Reply-To: <833aao5jew.fsf@gnu.org>

On Fri, May 29, 2009 at 12:48:39PM +0300, Eli Zaretskii wrote:
> > Date: Fri, 29 May 2009 09:35:33 +0000
> > Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
> > From: Alan Mackenzie <acm@muc.de>

> > > > Manuals shouldn't be patronising.  When a manual implicitly says
> > > > "if you can't even figure out what I mean by \"active\", you're
> > > > stupid", that's patronising.

> > > Did the manual actually say that? where?

> > No, it didn't _actually_ say that, it _implicitly_ said it; or, more
> > precisely, that's the message I would hear if I were an Emacs user
> > trying to make sense of that page of the manual.

> What text, exactly, could send such a message?

All the text using the obscure undefined word "active".




      reply	other threads:[~2009-05-29 13:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 12:29 Documentation of transient-mark-mode is sloppy, wrong, and confused Alan Mackenzie
2009-05-28 16:54 ` Chong Yidong
2009-05-28 20:15   ` Alan Mackenzie
2009-05-28 20:48     ` Chong Yidong
2009-05-28 23:03       ` Alan Mackenzie
2009-05-28 23:53         ` Davis Herring
2009-05-29 11:01           ` Alan Mackenzie
2009-05-29  0:21         ` Chong Yidong
2009-05-29  1:55         ` Stefan Monnier
2009-05-29  4:30           ` Kevin Rodgers
2009-05-29  5:47             ` Andreas Roehler
2009-05-29  8:25               ` Stephen J. Turnbull
2009-05-29  8:58                 ` Alan Mackenzie
2009-06-01  2:34                   ` Stephen J. Turnbull
2009-06-01  9:40                     ` Lennart Borgman
2009-06-02  6:23                     ` Andreas Roehler
2009-06-02 11:50                       ` Stephen J. Turnbull
2009-05-29  8:37           ` Eli Zaretskii
2009-05-29  9:27             ` Alan Mackenzie
2009-05-29 10:11               ` Eli Zaretskii
2009-05-29 13:13                 ` Alan Mackenzie
2009-05-29 14:19                 ` Stefan Monnier
2009-05-29 16:40                   ` Drew Adams
2009-05-29 22:20                     ` Alan Mackenzie
2009-05-30  0:11                       ` Drew Adams
2009-05-29  9:55             ` Stephen J. Turnbull
2009-05-29 10:14               ` Eli Zaretskii
2009-06-01  2:09                 ` Stephen J. Turnbull
2009-05-29 10:45               ` Andreas Roehler
2009-05-29  8:38         ` Eli Zaretskii
2009-05-29  9:35           ` Alan Mackenzie
2009-05-29  9:48             ` Eli Zaretskii
2009-05-29 13:17               ` Alan Mackenzie [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

  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=20090529131736.GF2793@muc.de \
    --to=acm@muc.de \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).