From: "B. T. Raven" <ecinmn@alcisp.com>
Subject: Intrusive spaces
Date: Wed, 7 Jun 2006 11:20:16 -0500 [thread overview]
Message-ID: <12e5c$4486fcc6$49edeed$27185@DIALUPUSA.NET> (raw)
I ran M-| bc on this region:
define fact(n) {
if (n <= 1) return (n);
return (n * fact(n-1));
}
fact(666)
The resulting very big number fills about 24 lines each terminated with
C-j. I then ran the following function
(defun unfill-paragraph () ;; bound to C-x M-q
"Do the opposite of fill-paragraph; stuff all lines in the current
paragraph into a single long line."
(interactive)
(let ((fill-column 90002000))
(fill-paragraph nil)))
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.
???
Thanks,
Ed
--
next reply other threads:[~2006-06-07 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 16:20 B. T. Raven [this message]
2006-06-08 8:01 ` Intrusive spaces Mathias Dahl
-- 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='12e5c$4486fcc6$49edeed$27185@DIALUPUSA.NET' \
--to=ecinmn@alcisp.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).