From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Why having string-chop-newline
Date: Wed, 30 Dec 2020 10:22:07 +0100 [thread overview]
Message-ID: <20201230092207.GB4367@tuxteam.de> (raw)
In-Reply-To: <CAO=W_ZpJDkpB_qhwxZD-G53b94auDXxkW-q0_o+uOaRgpWB7Vg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 255 bytes --]
On Wed, Dec 30, 2020 at 12:06:39PM +0300, Evgeny Zajcev wrote:
> Why is `string-chop-newline' needed?
FWIW, "my" Emacs has no function named like that. Perhaps you
should give us a hint towards where you found it, to help set
the context...
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-12-30 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 9:06 Why having string-chop-newline Evgeny Zajcev
2020-12-30 9:22 ` tomas [this message]
2020-12-30 11:56 ` Stefan Kangas
2020-12-30 12:08 ` tomas
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=20201230092207.GB4367@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-devel@gnu.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).