From: tomas@tuxteam.de
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: filemananger for emacs with meta information about a file without opening it
Date: Thu, 3 Nov 2022 09:44:09 +0100 [thread overview]
Message-ID: <Y2N/Wa3GMCrQ7lCW@tuxteam.de> (raw)
In-Reply-To: <CAP_d_8X4nFoPn8D4EjPoPVNvvx6v_Y_Niw_3m-rO=4SaNq3GRQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
On Thu, Nov 03, 2022 at 03:17:18PM +0700, Yuri Khan wrote:
> On Thu, 3 Nov 2022 at 14:58, <tomas@tuxteam.de> wrote:
>
> > > In Dired, one uses `y' to get basic information about the file without
> > > opening it. Often I use it for pictures to find out the resolution.
> >
> > How do you find out a picture's resolution without opening the file?
>
> Nohow. The opening is just not perceived by the user. The pedantic
> description would probably be “without visiting in a buffer and
> without starting an associated interactive application”.
Ah. Visiting a buffer was the elephant I was missing in the room :)
Thanks
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-11-03 8:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 20:49 filemananger for emacs with meta information about a file without opening it Uwe Brauer
2022-11-02 12:26 ` Michael Heerdegen
2022-11-03 9:14 ` Uwe Brauer
2022-11-03 9:20 ` Emanuel Berg
2022-11-03 15:44 ` Uwe Brauer
2022-11-03 15:49 ` Emanuel Berg
2022-11-04 13:05 ` Uwe Brauer
2022-11-04 13:43 ` Eli Zaretskii
2022-11-04 17:48 ` Marcin Borkowski
2022-11-04 5:13 ` [External] : " Drew Adams
2022-11-04 7:28 ` Uwe Brauer
2022-11-04 16:00 ` Drew Adams
2022-11-05 13:50 ` Jean Louis
2022-11-05 21:05 ` Drew Adams
2022-11-03 6:49 ` Jean Louis
2022-11-03 7:56 ` tomas
2022-11-03 8:17 ` Yuri Khan
2022-11-03 8:44 ` tomas [this message]
2022-11-03 11:15 ` Michael Heerdegen
2022-11-04 3:22 ` Jean Louis
2022-11-04 3:21 ` Jean Louis
2022-11-03 9:01 ` Emanuel Berg
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=Y2N/Wa3GMCrQ7lCW@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
--cc=yuri.v.khan@gmail.com \
/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).