From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: Speed of keyboard macro execution?
Date: Thu, 10 Dec 2015 19:15:53 +0100 [thread overview]
Message-ID: <87poyeyxt2.fsf@Rainer.invalid> (raw)
In-Reply-To: 83r3iu9rvp.fsf@gnu.org
Eli Zaretskii writes:
> After all, how frequently do you need to edit files with lines in
> excess of 11K characters?
If editing includes just opening the file and navigating around most of
the time, then the answer to that question for me is "daily". And the
lines are in fact a lot longer than 11k characters also, being tabulated
data with a few thousand columns, each 20 characters wide typically. I
can guarantee that there are no multi-byte or non-printing characters in
those files if that would make a difference.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2015-12-10 18:15 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 21:39 Speed of keyboard macro execution? Perry E. Metzger
2015-12-09 22:13 ` David Engster
2015-12-09 23:03 ` Perry E. Metzger
2015-12-10 16:43 ` Eli Zaretskii
2015-12-10 17:00 ` Perry E. Metzger
2015-12-10 17:14 ` John Wiegley
2015-12-10 17:27 ` David Engster
2015-12-10 17:33 ` Perry E. Metzger
2015-12-10 17:39 ` David Engster
2015-12-10 17:53 ` Eli Zaretskii
2015-12-10 18:10 ` Perry E. Metzger
2015-12-10 18:41 ` Eli Zaretskii
2015-12-10 18:44 ` David Kastrup
2015-12-10 18:57 ` Eli Zaretskii
2015-12-10 19:38 ` David Kastrup
2015-12-10 20:00 ` Eli Zaretskii
2015-12-10 20:09 ` David Kastrup
2015-12-10 20:43 ` Eli Zaretskii
2015-12-10 20:55 ` David Kastrup
2015-12-10 20:16 ` Perry E. Metzger
2015-12-10 20:18 ` John Wiegley
2015-12-10 20:36 ` David Kastrup
2015-12-10 20:43 ` John Wiegley
2015-12-10 21:01 ` David Kastrup
2015-12-10 21:26 ` John Wiegley
2015-12-10 23:35 ` David Kastrup
2015-12-11 1:14 ` John Wiegley
2015-12-11 6:27 ` David Kastrup
2015-12-12 22:56 ` John Wiegley
2015-12-12 23:46 ` David Kastrup
2015-12-13 0:16 ` John Wiegley
2015-12-13 0:32 ` David Kastrup
2015-12-12 23:20 ` Per Starbäck
2015-12-12 16:51 ` Perry E. Metzger
2015-12-12 17:42 ` David Kastrup
2015-12-12 23:01 ` Disabling visual lines for macros (was: Speed of keyboard macro execution?) John Wiegley
2015-12-12 23:33 ` Disabling visual lines for macros David Kastrup
2015-12-10 20:45 ` Speed of keyboard macro execution? Perry E. Metzger
2015-12-10 20:50 ` John Wiegley
2015-12-10 20:48 ` Eli Zaretskii
2015-12-10 20:50 ` John Wiegley
2015-12-10 21:13 ` David Kastrup
2015-12-10 17:37 ` Eli Zaretskii
2015-12-10 17:43 ` John Wiegley
2015-12-10 17:54 ` Eli Zaretskii
2015-12-10 18:15 ` Achim Gratz [this message]
2015-12-10 18:47 ` Eli Zaretskii
2015-12-12 2:14 ` Joseph Mingrone
2015-12-12 7:39 ` Eli Zaretskii
2015-12-12 17:28 ` Joseph Mingrone
2015-12-12 17:57 ` Eli Zaretskii
2015-12-12 18:12 ` Joseph Mingrone
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=87poyeyxt2.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).