From: miranda@pulusound.fi
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 64164@debbugs.gnu.org
Subject: bug#64164: 29.0.92; buffer-file-coding-system changes unexpectedly after saving
Date: Tue, 20 Jun 2023 12:22:22 +0300 [thread overview]
Message-ID: <c60b7ff94c1dfb68a2b5d69fc319e497@pulusound.fi> (raw)
In-Reply-To: <24e2cd85-0f23-40a9-838a-3eb7e2c1877f@pulusound.fi>
On 2023-06-20 01:29, miranda kastemaa wrote:
> 19 Jun 2023 20.36.06 Michael Albinus <michael.albinus@gmx.de>:
>> Well, if Tramp detects a remote macOS system, it converts the coding
>> system to `utf-8-hfs-mac', see function
>> `tramp-open-connection-setup-interactive-shell'. This heuristic works
>> for many years w/o complaints from users.
>
> thank you for pointing me towards this function. it is late here but
> this will help me do some more digging tomorrow.
after looking at `tramp-open-connection-setup-interactive-shell` a
little, i wonder whether the coding system here is the relevant one. if
i understand correctly, this seems to be setting the coding system for
the connection process, rather than the individual file buffers. on both
29.0.92 and 28.2, the Tramp debug output here is:
> tramp-open-connection-setup-interactive-shell (5) # Setting coding
> system to ‘utf-8-hfs’ and ‘utf-8-hfs-mac’
neither of which is a -unix coding system as (initially) reported by
`buffer-file-coding-system`.
opening files produces more debug output, but i failed to find any more
salient info in it (i tried searching for "coding", "utf", "-unix",
"-mac" etc).
let me know if you have any further suggestions for debugging.
best,
miranda
next prev parent reply other threads:[~2023-06-20 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:57 bug#64164: 29.0.92; buffer-file-coding-system changes unexpectedly after saving miranda
2023-06-19 16:55 ` Eli Zaretskii
2023-06-19 20:46 ` miranda kastemaa
2023-06-19 17:35 ` Michael Albinus
2023-06-19 22:29 ` miranda kastemaa
2023-06-20 9:22 ` miranda [this message]
2023-08-03 15:04 ` Michael Albinus
2023-08-28 11:03 ` Michael Albinus
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=c60b7ff94c1dfb68a2b5d69fc319e497@pulusound.fi \
--to=miranda@pulusound.fi \
--cc=64164@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).