unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stephen.berman@gmx.net, emacs-devel@gnu.org
Subject: RE: emacs-25 f708cb2: Clarify doc string of 'transpose-sexps'
Date: Fri, 4 Nov 2016 12:36:32 -0700 (PDT)	[thread overview]
Message-ID: <da4813cd-e7a6-49cc-9f80-7b89a60ab050@default> (raw)
In-Reply-To: <<83oa1vjdrx.fsf@gnu.org>>

> > It is really not great to tell someone they "cannot" or
> > "must not" etc. do something without raising an error that
> > really enforces "cannot" etc.
> 
> If someone comes up with a way to lift that restriction, we could
> remove this text from the doc string.  but as long as the command
> works as it does, I think we should document that, or else we will
> have bug reports about its not meeting expectations.

I did not suggest removing the text from the doc string.

The point is that it is better if the code backs up what
the doc says, by raising an error if you try to do what
it says you cannot do.

If `C-b' at bob did not raise an error, but instead just
moved point to the end of line 42, it would be scant help
to tell users in the doc of `C-b' that you cannot use it
at bob.



       reply	other threads:[~2016-11-04 19:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<20161104095223.23249.72530@vcs.savannah.gnu.org>
     [not found] ` <<20161104095223.631AB22012D@vcs.savannah.gnu.org>
     [not found]   ` <<8737j7e3r5.fsf@gmx.net>
     [not found]     ` <<ba4a000f-c63d-4fde-94b9-d493e895b7c7@default>
     [not found]       ` <<87y40zckn9.fsf@gmx.net>
     [not found]         ` <<977b7eaa-1c5f-4d8b-be5d-33ec73f5a962@default>
     [not found]           ` <<87twbncgve.fsf@gmx.net>
     [not found]             ` <<3687e9ab-658b-49b9-b766-8658d5c48374@default>
     [not found]               ` <<87pombceyc.fsf@gmx.net>
     [not found]                 ` <<83cd67b5-cb42-4fea-b6be-21e9ec8075a7@default>
     [not found]                   ` <<83oa1vjdrx.fsf@gnu.org>
2016-11-04 19:36                     ` Drew Adams [this message]
     [not found] <20161104095223.23249.72530@vcs.savannah.gnu.org>
     [not found] ` <20161104095223.631AB22012D@vcs.savannah.gnu.org>
2016-11-04 14:09   ` emacs-25 f708cb2: Clarify doc string of 'transpose-sexps' Stephen Berman
2016-11-04 14:31     ` Drew Adams
2016-11-04 15:47       ` Stephen Berman
2016-11-04 16:44         ` Drew Adams
2016-11-04 17:08           ` Stephen Berman
2016-11-04 17:21             ` Drew Adams
2016-11-04 17:50               ` Stephen Berman
2016-11-04 18:00                 ` Drew Adams
2016-11-04 18:33                   ` Eli Zaretskii
2016-11-04 18:30                 ` Eli Zaretskii
2016-11-04 18:26               ` Eli Zaretskii
2016-11-04 18:14       ` Eli Zaretskii

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=da4813cd-e7a6-49cc-9f80-7b89a60ab050@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen.berman@gmx.net \
    /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).