From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: 24766@debbugs.gnu.org
Subject: bug#24766: 26.0.50: [PATCH] Confusing behaviour for indent-relative-maybe
Date: Sat, 22 Oct 2016 22:21:51 +0300 [thread overview]
Message-ID: <83lgxgp4ts.fsf@gnu.org> (raw)
In-Reply-To: <8760ok8ays.fsf@gmail.com> (message from Alex on Sat, 22 Oct 2016 13:01:15 -0600)
> From: Alex <agrambot@gmail.com>
> Date: Sat, 22 Oct 2016 13:01:15 -0600
>
> In emacs -Q's scratch buffer, try the following:
>
> M-: (indent-relative) RET
>
> Repeating this will move to the next appropriate indentation point as
> indicated in indent-relative's docstring.
>
> Now try:
>
> M-: (indent-relative-maybe) RET
>
> The point does not move even when there are appropriate indentation
> points to move to.
It doesn't move because that's what UNINDENTED-OK means.
> This contradicts the intention of the docstring for
> indent-relative-maybe:
>
> If the previous nonblank line has no indent points beyond the
> column point starts at, this command does nothing.
>
>
> I would have expected, in indent-relative, that the calculation of a
> suitable indentation position is done independent of the argument
> UNINDENTED-OK. The following diff fixes this:
These functions exist for ages in this form. I agree that the doc
string is misleading (and the optional argument of indent-relative is
not even documented), but other than fixing the documentation, I see
no reason to change the behavior. Am I missing something?
next prev parent reply other threads:[~2016-10-22 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 19:01 bug#24766: 26.0.50: [PATCH] Confusing behaviour for indent-relative-maybe Alex
2016-10-22 19:21 ` Eli Zaretskii [this message]
2016-10-22 19:40 ` Alex
2016-10-22 19:48 ` Eli Zaretskii
2016-10-22 21:49 ` Alex
2016-10-23 6:23 ` Eli Zaretskii
2016-10-23 20:43 ` Alex
2016-10-24 8:23 ` Eli Zaretskii
2016-10-24 19:27 ` Alex
2016-10-24 19:57 ` Eli Zaretskii
2016-11-08 1:53 ` Alex
2016-11-08 15:07 ` Eli Zaretskii
2016-11-08 19:09 ` Alex
2016-11-08 20:26 ` Eli Zaretskii
2016-11-18 9:04 ` 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=83lgxgp4ts.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24766@debbugs.gnu.org \
--cc=agrambot@gmail.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 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).