all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: xfq.free@gmail.com, stephen.berman@gmx.net, 13810@debbugs.gnu.org
Subject: bug#13810: 24.3.50; Docstring of `newline' is confusing
Date: Sat, 25 Jan 2020 20:29:53 +0200	[thread overview]
Message-ID: <83ftg3pexq.fsf@gnu.org> (raw)
In-Reply-To: <87ftg376oe.fsf@marxist.se> (message from Stefan Kangas on Sat, 25 Jan 2020 19:05:37 +0100)

> From: Stefan Kangas <stefan@marxist.se>
> Cc: xfq.free@gmail.com,  stephen.berman@gmx.net,  13810@debbugs.gnu.org
> Date: Sat, 25 Jan 2020 19:05:37 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Linefeed is not RET, nor "newline".  It's C-j.
> 
> Where is this documented?

It's that character's official name, and supposed to be "common
knowledge".  Go to the end of any line in an Emacs buffer, and type
"C-u C-x =" -- Emacs will show the name of the character in the *Help*
buffer it pops up.





  reply	other threads:[~2020-01-25 18:29 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 [this message]
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
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=83ftg3pexq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13810@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    --cc=stephen.berman@gmx.net \
    --cc=xfq.free@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 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.