From: "Veli-Pekka Tätilä" <vtatila@gmailRemoveToReply.com>
To: help-gnu-emacs@gnu.org
Subject: Fill Prefix Qs: Smarter Inference, Paragraphs by Their Repeat Count, Making Them Read-only
Date: Mon, 1 Sep 2008 09:08:16 +0300 [thread overview]
Message-ID: <48bb8632$0$23599$9b536df3@news.fv.fi> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1956 bytes --]
Hi list,
After doing some studying on my own I can now better rephrase one of my key
questions about citing e-mail and news posts.
Briefly put:
How do I make emacs: a) infer the fil prefix from a line, b) make paragraphs
a set of contiguous lines with the same fill prefix repeat count, c) protect
the fill prefix from editing?
I really like refill mode legally blind, it let's me concentrate on the text
rather than caring about line breaks. Snipping quoted text then becomes a
matter of setting the appropriate fill prefix and editing the paragraph in
question. I can also just regexp search for the next level n quote (
^\(>\s-?\)\{n\} ) and kill from my search start position to the destination
quite easily. Pretty nice.
The only things Emacs does not do is infer the fill prefix directly from
line beginning, set paragraphs to be equal to a particular quoting level
(fill prefix n times), and make sure that I don't snip the fill prefix (>)
when killing sentences, for instance. So the question is, can it do these
three?
I have looked at various modes like post, filladapt and so on but none of
these are quite what I'm looking for. The best solution I can think of right
now is to simply use single space indentation for e-mail quoting levels and
convert between the equivalent number of spaces and > signs via a global
regexp replace both before, and after writing. Maybe that will due the trick
once I get used to it.
it still doesn't protect killing and movement in textual units like
sentences and beginnings of a line, I guess, and neither does it handle code
snippets with indentation.
If Emacs can manage the > signs on its own, there's absolutely no need for
me to cursor to them let alone edit them, much the same attitude as levels
of indent in code in a smart IDE.
Any help appreciated.
--
With kind regards Veli-Pekka Tätilä
Accessibility, Apps and Coding plus Synths and Music:
http://vtatila.kapsi.fi
next reply other threads:[~2008-09-01 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 6:08 Veli-Pekka Tätilä [this message]
2008-09-01 14:21 ` Fill Prefix Qs: Correction Veli-Pekka Tätilä
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='48bb8632$0$23599$9b536df3@news.fv.fi' \
--to=vtatila@gmailremovetoreply.com \
--cc=help-gnu-emacs@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.
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).