emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#20309: closed (25.0.50; Coding conversion error du


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#20309: closed (25.0.50; Coding conversion error during clojure-mode package upgrade)
Date: Tue, 22 Oct 2019 13:04:02 +0000

Your message dated Tue, 22 Oct 2019 16:03:12 +0300
with message-id <address@hidden>
and subject line Re: bug#20309: 25.0.50; Coding conversion error during 
clojure-mode package upgrade
has caused the debbugs.gnu.org bug report #20309,
regarding 25.0.50; Coding conversion error during clojure-mode package upgrade
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
20309: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20309
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.0.50; Coding conversion error during clojure-mode package upgrade Date: Sun, 12 Apr 2015 16:46:26 +0300
The package is being installed from MELPA, the file can be viewed at
http://melpa.org/packages/clojure-mode-20150410.2319.el.

Viewing it in the browser (or downloading and opening in `less')
displays those copyright characters just fine.

Not so here, see the attached screenshot.

Attachment: Screenshot from 2015-04-12 16:17:23.png
Description: Select coding system...

In GNU Emacs 25.0.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.12.2)
 of 2015-04-12 on axl
Repository revision: d0fcb21254394e22542dbc350220db3bafe0cc13
Windowing system distributor `The X.Org Foundation', version 11.0.11601901
System Description:     Ubuntu 14.10


--- End Message ---
--- Begin Message --- Subject: Re: bug#20309: 25.0.50; Coding conversion error during clojure-mode package upgrade Date: Tue, 22 Oct 2019 16:03:12 +0300 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
On 22.10.2019 3:57, Stefan Kangas wrote:
I can't reproduce this on current master.  I believe that it has been
fixed by the following commit (if not before)

Thank you for the reminder.

I haven't seen this lately, so: closing.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]