From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Speedup of display of long and truncated lines
Date: Sat, 13 Aug 2022 15:52:56 +0000 [thread overview]
Message-ID: <66bbbb95989005dd3e92@heytings.org> (raw)
In-Reply-To: <8335e0m9zp.fsf@gnu.org>
>>> I didn't yet look at C-v/M-v, mainly because I don't have examples of
>>> files with long lines that have enough long lines to justify movement
>>> by window-full. (I could, of course, produce such files myself, but
>>> the question is: do such files exist in Real Life, enough to make the
>>> scrolling commands important in these cases? Examples of such files,
>>> if they exist, are welcome.)
>>
>> Yes, such files exist in Real Life. An example are database dumps, in
>> which you can have hundreds of very long lines.
>
> Thanks, I'd appreciate any pointers to where I could download examples
> of such files.
>
I cannot share such an example myself alas, the real-life databases I have
access to contain business-sensitive data. But you can easily create a
similar file with the following script. Its two parameters are the number
of tables in the database and the number of elements in each table. 100
and 10000 are a good starting point (for what is still a small database).
#!/bin/bash
for i in $(seq 1 $1)
do
echo -n "INSERT INTO TABLE_$i VALUES "
for j in $(seq 1 $2)
do
echo -n "(10,'100','QWERTY','Foo Bar Baz',50,4852,$j)"
(($j == $2)) && echo -n ';' || echo -n ','
done
echo
done
next prev parent reply other threads:[~2022-08-13 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 14:10 Speedup of display of long and truncated lines Eli Zaretskii
2022-08-13 14:28 ` Stefan Monnier
2022-08-13 15:10 ` Eli Zaretskii
2022-08-13 15:34 ` Gregory Heytings
2022-08-13 15:36 ` Eli Zaretskii
2022-08-13 15:52 ` Gregory Heytings [this message]
2022-08-19 6:49 ` Eli Zaretskii
2022-08-20 16:22 ` Gregory Heytings
2022-08-21 11:22 ` Dmitry Gutov
2022-10-11 10:38 ` Eli Zaretskii
2022-08-14 13:42 ` Eli Zaretskii
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=66bbbb95989005dd3e92@heytings.org \
--to=gregory@heytings.org \
--cc=eliz@gnu.org \
--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).