From: Xue Fuqiao <xfq.free@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 13810@debbugs.gnu.org
Subject: bug#13810: 24.3.50; Docstring of `newline' is confusing
Date: Mon, 25 Feb 2013 21:35:22 +0800 [thread overview]
Message-ID: <20130225213522.e176a678f0f63acb1c2dd393@gmail.com> (raw)
In-Reply-To: <87k3pwsf98.fsf@rosalinde.fritz.box>
On Mon, 25 Feb 2013 14:18:59 +0100
Stephen Berman <stephen.berman@gmx.net> wrote:
> >> > In the doc string of the function `newline':
> >> > Insert a newline, and move to left margin of the new line if it's
> >> > blank.
> >> > To reproduce this bug:
> >> > emacs -Q
> >> > M-<
> >> > M-: (newline) RET
> >> > A new line appears, but the point doesn't move to left margin of the
> >> > first line.
> >> I think you misread the doc string: point should -- and does -- move to
> >> the left margin of the *new* line.
> > You mean the *new* line is the second line (now)?
> In the doc string the two
> words "new line" unambiguously refer to the line after the inserted
> newline character that results from calling newline, but the first word
> "newline" should perhaps be replaced by "newline character" or "line
> feed".
Sounds fine for me.
> Steve Berman
--
Best regards, Xue Fuqiao.
http://www.emacswiki.org/emacs/XueFuqiao
next prev parent reply other threads:[~2013-02-25 13:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 10:03 bug#13810: 24.3.50; Docstring of `newline' is confusing Xue Fuqiao
2013-02-25 12:23 ` Stephen Berman
2013-02-25 12:48 ` Xue Fuqiao
2013-02-25 13:05 ` Stephen Berman
2013-02-25 13:27 ` Xue Fuqiao
2013-02-25 15:50 ` Eli Zaretskii
2013-02-25 22:33 ` Xue Fuqiao
2013-02-26 3:46 ` Eli Zaretskii
2020-01-25 15:39 ` Stefan Kangas
2020-01-25 17:20 ` Eli Zaretskii
2020-01-25 18:05 ` Stefan Kangas
2020-01-25 18:29 ` Eli Zaretskii
2013-02-25 15:30 ` Stefan Monnier
2013-02-25 16:43 ` Stephen Berman
2013-02-25 13:18 ` Stephen Berman
2013-02-25 13:35 ` Xue Fuqiao [this message]
2020-09-21 14:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130225213522.e176a678f0f63acb1c2dd393@gmail.com \
--to=xfq.free@gmail.com \
--cc=13810@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.