emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#24860: closed (24.5; doc string of `transpose-sexp


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#24860: closed (24.5; doc string of `transpose-sexps')
Date: Fri, 04 Nov 2016 09:58:01 +0000

Your message dated Fri, 04 Nov 2016 11:58:11 +0200
with message-id <address@hidden>
and subject line Re: bug#24860: 24.5; doc string of `transpose-sexps'
has caused the debbugs.gnu.org bug report #24860,
regarding 24.5; doc string of `transpose-sexps'
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24860: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24860
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.5; doc string of `transpose-sexps' Date: Wed, 2 Nov 2016 11:08:54 -0700 (PDT)
1. This part of the doc string is unclear.  I have no idea what it is
really trying to say.

  Does not work on a sexp that point is in the middle of
  if it is a list or string.

What does "does not work" mean?  Raises an error?  Does something that
we cannot describe?  Does nothing?

When point is in the middle of a list it can also be between two sexps,
which themselves could be lists: ((foo)|(bar)), with point at |.  What
"does not work" in that case, with an ARG of 1?

This part of the doc is completely unclear.  What's more, it is not
mentioned in the Emacs manual (node `Expressions').

2. The doc string needs to say, as does the manual (node `Expressions'),
that a zero ARG has particular behavior (and describe it) - it is not a
no-op.

3. I think it would help for the manual (node `Expressions') to give a
simple example showing the usefulness of the zero ARG case.  It's not
too clear from the description why this behavior is provided.


In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/usr --host=i686-pc-mingw32'



--- End Message ---
--- Begin Message --- Subject: Re: bug#24860: 24.5; doc string of `transpose-sexps' Date: Fri, 04 Nov 2016 11:58:11 +0200
> Date: Wed, 2 Nov 2016 11:08:54 -0700 (PDT)
> From: Drew Adams <address@hidden>
> 
> 1. This part of the doc string is unclear.  I have no idea what it is
> really trying to say.
> 
>   Does not work on a sexp that point is in the middle of
>   if it is a list or string.
> 
> What does "does not work" mean?  Raises an error?  Does something that
> we cannot describe?  Does nothing?

Depending on what are the surrounding sexps and where point is, it
could do any of the above.

> When point is in the middle of a list it can also be between two sexps,
> which themselves could be lists: ((foo)|(bar)), with point at |.  What
> "does not work" in that case, with an ARG of 1?
> 
> This part of the doc is completely unclear.

Since the doc string starts by saying "Like M-t", its intent was to
contrast the behavior against that of transpose-words, where point
could be both between the words and in the middle of a word, in order
to have that word transposed with the next one.  That doesn't work
with sexps.

> What's more, it is not mentioned in the Emacs manual (node
> `Expressions').

It is mentioned, in a way, because the manual says C-M-t is analogous
to C-t, i.e. it doesn't start from M-t.

I clarified this aspect in the doc string.

> 2. The doc string needs to say, as does the manual (node `Expressions'),
> that a zero ARG has particular behavior (and describe it) - it is not a
> no-op.

Added.

> 3. I think it would help for the manual (node `Expressions') to give a
> simple example showing the usefulness of the zero ARG case.  It's not
> too clear from the description why this behavior is provided.

Volunteers are welcome to come up with useful examples, but I think
the bug report can now be closed, as the zero argument case doesn't
have examples in other similar commands as well.

Thanks.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]