From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Bind 'w' to a more useful function
Date: Tue, 31 Aug 2010 13:29:41 -0500 [thread overview]
Message-ID: <87lj7m3aay.fsf@lifelogs.com> (raw)
In-Reply-To: <m3tyma7wkr.fsf@quimbies.gnus.org>
On Tue, 31 Aug 2010 15:15:00 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Leo <sdl.web@gmail.com> writes:
>> I guess it is hard to do it right all the time. For example, I have read
>> emails with long lines mixed with code snippets. I like the long lines
>> to be filled but that usually screws up the code.
LMI> Yes. So we need a code snippet that's able to look at a (long) line and guess whether it's natural text or something else.
LMI> One heuristic would be if there's a lot of short word-constituent elements, and not too much space.
LMI> I mean, the following paragraph has a different signature in that dept than
LMI> (process (start-process
LMI> "images" nil "curl"
LMI> "-s" "--create-dirs"
LMI> to take a random example from a buffer. (This message isn't filled so that I can use it as a test case.)
I'm not optimistic. Maybe Lisp+English will work, but natural text is
really hard to parse and source code too.
Ted
next prev parent reply other threads:[~2010-08-31 18:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 17:28 Leo
2007-07-02 19:00 ` Reiner Steib
2007-07-02 19:55 ` Leo
2007-07-02 20:13 ` Reiner Steib
2010-08-30 23:01 ` Lars Magne Ingebrigtsen
2010-08-31 3:25 ` Leo
2010-08-31 13:00 ` Lars Magne Ingebrigtsen
2010-08-31 13:08 ` Leo
2010-08-31 13:15 ` Lars Magne Ingebrigtsen
2010-08-31 16:34 ` Leo
2010-08-31 18:29 ` Ted Zlatanov [this message]
2010-08-31 18:33 ` Lars Magne Ingebrigtsen
2010-08-31 19:00 ` Ted Zlatanov
2010-08-31 19:03 ` Lars Magne Ingebrigtsen
2010-08-31 19:12 ` Ted Zlatanov
2010-09-01 8:46 ` Steinar Bang
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=87lj7m3aay.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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 NNTP newsgroup(s).