From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 60929@debbugs.gnu.org
Subject: bug#60929: 30.0.50; [FR] `file-name-extension' and backup suffixes
Date: Tue, 24 Jan 2023 14:37:27 +0200 [thread overview]
Message-ID: <83y1psglbs.fsf@gnu.org> (raw)
In-Reply-To: <87cz745gqp.fsf@localhost> (message from Ihor Radchenko on Tue, 24 Jan 2023 11:12:56 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: 60929@debbugs.gnu.org
> Date: Tue, 24 Jan 2023 11:12:56 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> Hmm... If we go further into generalization, what I am talking about is
> centralized API to "describe" current buffer file:
>
> 1. What is already there:
>
> - `buffer-file-name'
> - `buffer-file-truename'
> - `buffer-file-number'
>
> 2. What could be made available:
>
> - TRAMP mount point
> - `buffer-effective-name'
> - some info + callback to re-encrypt/re-archive/re-apply suffixes
> for a given file buffer onto another file buffer.
>
> > For example, if you want the file name so you could know the
> > appropriate major mode, perhaps a better interface would be to give
> > you a list of relevant major modes?
>
> I am not sure what you refer to here.
I mean:
. given "foo.org.~10~" return the list ("foo" org-mode backup)
. given "foo.org.gpg.gz" return ("foo" org-mode epa-file compress)
etc.
next prev parent reply other threads:[~2023-01-24 12:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 10:50 bug#60929: 30.0.50; [FR] `file-name-extension' and backup suffixes Ihor Radchenko
2023-01-18 11:08 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-18 12:47 ` Eli Zaretskii
2023-01-18 13:01 ` Ihor Radchenko
2023-01-18 14:47 ` Eli Zaretskii
2023-01-23 10:05 ` Ihor Radchenko
2023-01-23 13:34 ` Eli Zaretskii
2023-01-24 11:12 ` Ihor Radchenko
2023-01-24 12:37 ` Eli Zaretskii [this message]
2023-01-25 13:18 ` Ihor Radchenko
2023-01-25 13:26 ` Eli Zaretskii
2023-01-25 13:33 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-25 13:43 ` Ihor Radchenko
2023-01-25 13:37 ` Ihor Radchenko
2023-01-18 14:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y1psglbs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60929@debbugs.gnu.org \
--cc=yantar92@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.