From: Marco Patzer <homerow@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Find too long sentences
Date: Fri, 15 Feb 2013 15:52:23 +0100 [thread overview]
Message-ID: <20130215145223.GI3733@homerow> (raw)
In-Reply-To: <511E41F6.5070707@mmnetz.de>
[-- Attachment #1.1: Type: text/plain, Size: 1135 bytes --]
On 2013–02–15 "H. Özoguz" wrote:
> Which text editor can do that, find too long sentences?
None, since no editor knows by default what “too long” is. But a few
editors (at least vim and I assume emacs as well) have an idea of
what a sentence is. Both are scriptable, which means you can tell
them what you consider “too long”. If you use a different editor
read the manual or ask your favourite search engine.
In vim pressing “vis” (visualise inner sentence) marks the current
sentence, then pressing “g<Ctrl-g>” yields:
Selected 2 of 4 lines; 14 of 50 words; 82 of 296 bytes
That means current sentence is 82 bytes long. The rest is up to you.
Pick a language you like, vim uses its own scripting language but
also has bindings for python, perl, lua, etc. Pseudo-code:
go to begin of file
start:
get byte length of sentence
if length > max_length
% do something
fi
move on to the next sentence
goto start
Or just define a regular expression for a sentence (google is your
friend) and use a scripting language directly if your editor is not
scriptable.
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-02-15 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.815.1360932936.2489.ntg-context@ntg.nl>
2013-02-15 14:11 ` "H. Özoguz"
2013-02-15 14:52 ` Marco Patzer [this message]
2013-02-15 16:16 ` Marco Patzer
2013-02-15 12:38 "H. Özoguz"
2013-02-15 12:52 ` Marco Patzer
2013-02-15 12:54 ` Philipp Gesang
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=20130215145223.GI3733@homerow \
--to=homerow@lavabit.com \
--cc=ntg-context@ntg.nl \
/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).