From: rvclayton@acm.org (R. Clayton)
To: John Mastro <john.b.mastro@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Newline-phobic text help.
Date: Fri, 15 Jul 2016 12:22:38 -0400 [thread overview]
Message-ID: <E1bO5ss-0005ki-2R@BanjaLuka.rclayton.net> (raw)
In-Reply-To: <CAOj2CQSHYyPn_7euABYN7fZ7oDMjZW13PmkR3o98aOaQFRj5yg@mail.gmail.com> (message from John Mastro on Thu, 14 Jul 2016 18:43:41 -0700)
Thanks for your reply to my message.
I think your scenario boils down to the fact that you don't want the
intra-paragraph newlines in your buffer to end up in your web form; if I got
that wrong, you can ignore what I wrote below.
Nope, you got it.
I don't know the answer to your question about controlling how newlines are
written, but perhaps another approach would be to:
You're being polite by not pointing out that using enriched-mode to do what I
want is a stupid idea. Apart from the hard-soft newlines problem, there's also
the header at the beginning of the file.
The only trick would be identifying when you've got an "It's All Text!"
buffer so you can evaluate that code.
I hacked around that like so: point iat to an editor that's the shim shell
script
emacs --exec '(defconst its-all-text! t)' $@
and put
(when (boundp? 'its-all-text!)
(auto-fill-mode -1)
(visual-line-mode))
in the text-mode-hook.
next prev parent reply other threads:[~2016-07-15 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 18:47 Newline-phobic text help R. Clayton
2016-07-15 1:43 ` John Mastro
2016-07-15 16:22 ` R. Clayton [this message]
2016-07-15 17:35 ` John Mastro
[not found] <mailman.1432.1468522060.26859.help-gnu-emacs@gnu.org>
2016-07-15 1:11 ` Emanuel Berg
2016-07-15 1:55 ` R. Clayton
[not found] ` <mailman.1457.1468547758.26859.help-gnu-emacs@gnu.org>
2016-07-15 2:08 ` Emanuel Berg
2016-07-15 4:45 ` Marcin Borkowski
[not found] ` <mailman.1459.1468557921.26859.help-gnu-emacs@gnu.org>
2016-07-15 5:36 ` Emanuel Berg
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=E1bO5ss-0005ki-2R@BanjaLuka.rclayton.net \
--to=rvclayton@acm.org \
--cc=help-gnu-emacs@gnu.org \
--cc=john.b.mastro@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.