From: Lars Ingebrigtsen <larsi@gnus.org>
To: John Helmert III <ajak@gentoo.org>
Cc: 58202@debbugs.gnu.org
Subject: bug#58202: [PATCH] Move point to end of line after indent for sieve-mode
Date: Sat, 01 Oct 2022 14:52:23 +0200 [thread overview]
Message-ID: <878rlzhfjs.fsf@gnus.org> (raw)
In-Reply-To: <20220930180728.327001-1-ajak@gentoo.org> (John Helmert, III's message of "Fri, 30 Sep 2022 13:07:28 -0500")
John Helmert III <ajak@gentoo.org> writes:
> * lisp/net/sieve-mode.el: move pointer to end of line after indenting
I'm not very familiar with sieve-mode, but moving the pointer to the end
of the line after indenting is pretty unusual for a mode. Why should
sieve-mode do this?
next prev parent reply other threads:[~2022-10-01 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 18:07 bug#58202: [PATCH] Move point to end of line after indent for sieve-mode John Helmert III
2022-10-01 12:52 ` Lars Ingebrigtsen [this message]
2022-10-01 14:54 ` John Helmert III
2022-10-02 12:06 ` Lars Ingebrigtsen
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=878rlzhfjs.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58202@debbugs.gnu.org \
--cc=ajak@gentoo.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).