From: Ihor Radchenko <yantar92@posteo.net>
To: Ruijie Yu <ruijie@netyu.xyz>
Cc: Eli Zaretskii <eliz@gnu.org>, 60929@debbugs.gnu.org
Subject: bug#60929: 30.0.50; [FR] `file-name-extension' and backup suffixes
Date: Wed, 25 Jan 2023 13:43:46 +0000 [thread overview]
Message-ID: <87k01alofh.fsf@localhost> (raw)
In-Reply-To: <sdvlelqenxj.fsf@fw.net.yu>
Ruijie Yu <ruijie@netyu.xyz> writes:
>> Talking about "opening the file" again narrows the scope of the
>> requested feature, IMO. We don't want to assume that the application
>> would like to open the file. Besides, Text mode does affect how Emacs
>> treats the file.
>
> Another thing to consider is when the mode is not activated via
> `auto-mode-alist' -- for example, via M-x major-mode. Consider what
> happens to the proposed file extension list when "foo.txt" and
> "bar.txt.bak.gpg" are manually activated as `org-mode'.
That's easy. One can simply check `major-mode' variable value.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-01-25 13:43 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
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 [this message]
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
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=87k01alofh.fsf@localhost \
--to=yantar92@posteo.net \
--cc=60929@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ruijie@netyu.xyz \
/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).