unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Mikhail Pomaznoy <mikpom@mikpom.ru>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Memory-efficient way of opening large files in Emacs read-only
Date: Thu, 08 Dec 2022 15:27:53 +0100	[thread overview]
Message-ID: <87sfhqdl7a.fsf@mbork.pl> (raw)
In-Reply-To: <8e91d0e8-2474-dd98-9bca-4606becd974d@mikpom.ru>


On 2022-12-08, at 03:49, Mikhail Pomaznoy <mikpom@mikpom.ru> wrote:

> Greetings!
>
> In my daily workflows I commonly stumble upon a task of peeking into
> a header of a large (sometimes compressed) file. Those files can
> commonly be gigabytes in compressed form so can't fit into
> memory. I was wondering how can this be done in Emacs to leverage its
> search and navigate capabilities?
>
> In a terminal this task is nicely accomplished with `less`, which
> loads file on demand while you scroll (memory-efficiently) and
> automatically detects at least gzip compression. However I am
> struggling to do something similar in Emacs for quite a long time.
> I tried VLF (requires manually switching chunks loaded, encountered
> problems with compression), view-file (loads everything in memory),
> running less in Emacs terminals (I prefer outside-Emacs terminals) but
> for various reasons all this solutions are suboptimal and I usually
> end up with using `less`.
>
> Is there something in Emacs I am missing? Is something like this makes
> sense to develop (I consider to write something for Emacs) ? I am
> using Emacs 28 and maybe in Emacs 29 there are novelties related to
> this issue?

I have no idea if Emacs has anything like this (I doubt), but the way
I'd go about it would be to either leverage `less' inside one of the
Emacs terminals or write some Elisp, colling to things like `gunzip' and
`head' and then putting the result into some buffer.  (I think you could
even make it so that scrolling down would load the next portion in the
background, à la modern Web.  While I /hate/ this behavior of websites,
here it could actually make sense.)

Best,

-- 
Marcin Borkowski
http://mbork.pl



  parent reply	other threads:[~2022-12-08 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  2:49 Memory-efficient way of opening large files in Emacs read-only Mikhail Pomaznoy
2022-12-08 14:13 ` Filipp Gunbin
2022-12-08 14:27 ` Marcin Borkowski [this message]
2022-12-09  3:03   ` Mikhail Pomaznoy
2022-12-09  5:21     ` tomas

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=87sfhqdl7a.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mikpom@mikpom.ru \
    /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).