From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Kenichi Handa <handa@gnu.org>
Cc: 15535@debbugs.gnu.org
Subject: bug#15535: Acknowledgement (24.3.50; basic-save-buffer should update buffer-file-coding-system value if the contents were written using different coding system)
Date: Sun, 06 Oct 2013 23:58:57 +0300 [thread overview]
Message-ID: <5251CF11.8080301@yandex.ru> (raw)
In-Reply-To: <83vc1a5omh.fsf@gnu.org>
On 06.10.2013 19:51, Eli Zaretskii wrote:
> If the former, we could perhaps add some flag to struct undecided_spec
> and set it whenever the encoder used by `undecided' sees a non-ASCII
> character, and then use that flag to set last-coding-system-used to
> UTF-8.
That already happens (last-coding-system-used has the right value right
after the file is written), but I don't think I can use it: even if
`ruby-mode-set-encoding' is moved to after-save-hook, as long as it's
not the first function in this hook (and I can't ensure that it is), the
previous functions can also do some I/O and thus change
last-coding-system-used's value.
And that the reason I reverted 114527 in 114533, which in turn sparked
the discussion in emacs-devel.
next prev parent reply other threads:[~2013-10-06 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 22:44 bug#15535: 24.3.50; basic-save-buffer should update buffer-file-coding-system value if the contents were written using different coding system Dmitry Gutov
[not found] ` <handler.15535.B.138101307530740.ack@debbugs.gnu.org>
2013-10-05 23:09 ` bug#15535: Acknowledgement (24.3.50; basic-save-buffer should update buffer-file-coding-system value if the contents were written using different coding system) Dmitry Gutov
2013-10-06 16:51 ` Eli Zaretskii
2013-10-06 20:58 ` Dmitry Gutov [this message]
2013-10-07 2:52 ` Eli Zaretskii
2013-10-07 4:00 ` Dmitry Gutov
2013-10-07 14:59 ` Kenichi Handa
2013-10-13 12:06 ` Kenichi Handa
2013-10-13 16:48 ` Eli Zaretskii
2013-10-13 20:43 ` Dmitry Gutov
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=5251CF11.8080301@yandex.ru \
--to=dgutov@yandex.ru \
--cc=15535@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=handa@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 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.