From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 35647@debbugs.gnu.org
Subject: bug#35647: Documentation and implementation of (move-to-column <n> t) differ.
Date: Thu, 09 May 2019 18:43:06 +0300 [thread overview]
Message-ID: <835zqjhbw5.fsf@gnu.org> (raw)
In-Reply-To: <20190509150537.GC11178@ACM> (message from Alan Mackenzie on Thu, 9 May 2019 15:05:37 +0000)
> Date: Thu, 9 May 2019 15:05:37 +0000
> Cc: 35647@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > Would you mind preparing a documentation patch for this issue?
>
> How about:
Fine with me, thanks.
Please push to the emacs-26 branch.
next prev parent reply other threads:[~2019-05-09 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 10:48 bug#35647: Documentation and implementation of (move-to-column <n> t) differ Alan Mackenzie
2019-05-09 14:04 ` Eli Zaretskii
2019-05-09 15:05 ` Alan Mackenzie
2019-05-09 15:43 ` Eli Zaretskii [this message]
2019-05-09 16:32 ` Alan Mackenzie
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=835zqjhbw5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35647@debbugs.gnu.org \
--cc=acm@muc.de \
/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).