From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: alex.branham@gmail.com, 34858@debbugs.gnu.org
Subject: bug#34858: indent-relative called with prefix calls tab-to-tab-stop
Date: Thu, 14 Mar 2019 22:18:56 +0200 [thread overview]
Message-ID: <83lg1h1a6n.fsf@gnu.org> (raw)
In-Reply-To: <87k1h15lob.fsf@gmail.com> (message from Alex on Thu, 14 Mar 2019 12:57:08 -0600)
> From: Alex <agrambot@gmail.com>
> Cc: alex.branham@gmail.com, 34858@debbugs.gnu.org
> Date: Thu, 14 Mar 2019 12:57:08 -0600
>
> Sorry, I wasn't clear. I meant that the special case here could be
> considered (trivially) equivalent to the case where the previous
> non-blank line has a single indent point at column zero, and therefore
> should be treated equivalently when FIRST-ONLY is non-nil
> (`tab-to-tab-stop` should not be called if on or past the first indent
> point, i.e., column 0).
But then we'd do nothing in that situation. How does it make sense?
> The usage of `beyond' does not change the behaviour when the starting
> column is on the first indent point, which outside of this special case
> is doing nothing.
When there are previous lines to align with, yes. But here there's
nothing before, so what is the justification for doing nothing?
next prev parent reply other threads:[~2019-03-14 20:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 15:35 bug#34858: indent-relative called with prefix calls tab-to-tab-stop Alex Branham
2019-03-14 16:00 ` Eli Zaretskii
2019-03-14 16:17 ` Alex Branham
2019-03-20 20:23 ` Filipp Gunbin
2019-03-25 23:06 ` Alex Branham
2019-03-26 15:39 ` Eli Zaretskii
2019-03-26 15:42 ` Alex Branham
2019-03-26 16:47 ` Eli Zaretskii
2019-04-02 0:11 ` Basil L. Contovounesios
2019-04-02 14:40 ` Eli Zaretskii
2019-04-03 17:12 ` Basil L. Contovounesios
2019-04-06 0:52 ` Alex Branham
2019-03-14 16:45 ` Alex
2019-03-14 18:02 ` Eli Zaretskii
2019-03-14 18:57 ` Alex
2019-03-14 20:18 ` Eli Zaretskii [this message]
2019-03-14 21:27 ` Alex
2019-03-15 4:52 ` 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=83lg1h1a6n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34858@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=alex.branham@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).