You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However I get an encoding problem when editing remote iso-latin-1 files in tramp mode, which ends up in utf-8 format no matter my local .emacs configuration, which says use latin-1 always.
If I edit the iso-latin-1 file locally, latin-1 encoding is kept through an update, so it seems to be related to the tramp mode.
I also believe the problem may be related to the base64 transfer and encode/decode, but not sure where the exact problem is located.
I downgraded back to emacs 28.2, and the problem is gone, so something seems to be introduced in 29.1.
Regards
Trond
The text was updated successfully, but these errors were encountered:
I reproduced this issue also on windows and linux while using emacs29.1, so it seems to be a bug on that version of emacs itself.
Using the newest versions of tramp could avoid the issue, and on the 29.1 the patch attached here may fixes.
However, I suppose updating 29.2 would be a good idea (although it is not released yet, but it seems to be fixed on that version).
On Mac, I upgraded to emacs 29.1.
However I get an encoding problem when editing remote iso-latin-1 files in tramp mode, which ends up in utf-8 format no matter my local .emacs configuration, which says use latin-1 always.
If I edit the iso-latin-1 file locally, latin-1 encoding is kept through an update, so it seems to be related to the tramp mode.
I also believe the problem may be related to the base64 transfer and encode/decode, but not sure where the exact problem is located.
I downgraded back to emacs 28.2, and the problem is gone, so something seems to be introduced in 29.1.
Regards
Trond
The text was updated successfully, but these errors were encountered: