From: Mathias Dahl <brakjoller@gmail.com>
Subject: Re: Intrusive spaces
Date: Thu, 08 Jun 2006 10:01:04 +0200 [thread overview]
Message-ID: <uhd2w6pq7.fsf@gmail.com> (raw)
In-Reply-To: 12e5c$4486fcc6$49edeed$27185@DIALUPUSA.NET
"B. T. Raven" <ecinmn@alcisp.com> writes:
> on those 24 lines. Instead of joining them seamlessly, it puts in a space
> where the C-j had been. I haven't noticed this happening with ordinary
> text before. This happens with 21.3 on dos shell msw98.
I agree with the other reply, that I would expect a space to separate
what was originally a newline character.
Anyway, why not just search and replace all newlines with an empty
string. Something like this should work:
(defun replace-newline-with-nothing ()
(while (search-forward-regexp "\n" nil t)
(replace-match "")))
next prev parent reply other threads:[~2006-06-08 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 16:20 Intrusive spaces B. T. Raven
2006-06-08 8:01 ` Mathias Dahl [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-07 17:34 Jay Bingham
[not found] <mailman.2718.1149703362.9609.help-gnu-emacs@gnu.org>
2006-06-07 22:20 ` B. T. Raven
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=uhd2w6pq7.fsf@gmail.com \
--to=brakjoller@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.
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).