[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Issues installing packages from melpa
From: |
Akber Khan |
Subject: |
RE: Issues installing packages from melpa |
Date: |
Wed, 29 Sep 2021 14:03:56 +0000 |
Hi all,
Here's my output from C-h v file-name-handler-alist:
file-name-handler-alist is a variable defined in C source code .
Its value is
(("\\`\\(.+\\.\\(?:7z\\|CAB\\|LZH\\|MSU\\|ZIP\\|a\\(?:pk\\|r\\)\\|c\\(?:ab\\|pio\\)\\|de\\(?:b\\|pot\\)\\|exe\\|iso\\|jar\\|lzh\\|m\\(?:su\\|tree\\)\\|od[bfgpst]\\|pax\\|r\\(?:ar\\|pm\\)\\|shar\\|t\\(?:ar\\|bz\\|gz\\|lz\\|xz\\|zst\\)\\|warc\\|x\\(?:ar\\|p[is]\\)\\|zip\\)\\(?:\\.\\(?:Z\\|bz2\\|gz\\|l\\(?:rz\\|z\\(?:ma\\|[4o]\\)?\\)\\|uu\\|xz\\|zst\\)\\)*\\)\\(/.*\\)\\'"
. tramp-archive-autoload-file-name-handler)
("\\.gpg\\(~\\|\\.~[0-9]+~\\)?\\'" . epa-file-handler)
("\\(?:\\.tzst\\|\\.zst\\|\\.dz\\|\\.txz\\|\\.xz\\|\\.lzma\\|\\.lz\\|\\.g?z\\|\\.\\(?:tgz\\|svgz\\|sifz\\)\\|\\.tbz2?\\|\\.bz2\\|\\.Z\\)\\(?:~\\|\\.~[-[:alnum:]:#@^._]+\\(?:~[[:digit:]]+\\)?~\\)?\\'"
. jka-compr-handler)
("\\`/[^/|:]+:" . tramp-autoload-file-name-handler)
("\\`/:" . file-name-non-special))
I omitted the documentation portion of the output. Thank you Janelle, Philip,
and Tassilo for helping with this!
Best,
Akber
-----Original Message-----
From: Philip Kaludercic <philipk@posteo.net>
Sent: Tuesday, September 28, 2021 1:58 PM
To: Janelle Rose <Janelle.T.Rose@frb.gov>
Cc: Tassilo Horn <tsdh@gnu.org>; help-gnu-emacs@gnu.org; Akber Khan
<Akber.Khan@frb.gov>
Subject: Re: Issues installing packages from melpa
Janelle Rose <Janelle.T.Rose@frb.gov> writes:
> I will say the error is different based on the version of emacs that I use.
> When I use emacs 27.2, I get the option to install the package before it
> errors. I'll paste the text directly in the email if that makes it easier.
These seem to be the same error, just handled in different ways. In both cases
\213 indicates a gzip file that is not being handled properly. Could you check
the current value of file-name-handler-alist (use C-h v) to see if something is
missing.
This might be worth a bug report (M-x report-emacs-bug) to have more people
look at what might be the issue.
> Here is the output for 27.2
>
> Leaving directory
> /arc/home/m1jtr02/.emacs.d/elpa/abl-mode-20210923.950
>
>
> Compiling file
> /arc/home/m1jtr02/.emacs.d/elpa/abl-mode-20210923.950/abl-mode.el at
> Tue Sep 28 13:32:58 2021 Entering directory
> /arc/home/m1jtr02/.emacs.d/elpa/abl-mode-20210923.950/
> abl-mode.el:1:3:Warning: reference to free variable \213
> abl-mode.el:1:23:Warning: reference to free variable
> abl-mode.el:1:29:Warning: reference to free variable ko F s +
> abl-mode.el:1:49:Warning: reference to free variable ZS\201
> abl-mode.el:1:55:Error: Invalid read syntax: ")"
>
> Here is the output from emacs 26.3
>
> These default coding systems were tried to encode text
> in the buffer *temp* :
> (utf-8-unix (2 . 4194187) (11 . 4194189) (13 . 4194253) (15
> . 4194267) (18 . 4194238) (19 . 4194291) (23 . 4194194) (28
> . 4194195) (29 . 4194264) (30 . 4194275) (32 . 4194284)) However,
> each of them encountered characters it couldn t encode:
> utf-8-unix cannot encode these: \213 \215 \315 \333 \276 \363 \222
> \223 \330 \343
>
> Click on a character (or switch to this window by C-x o and select
> the characters by RET) to jump to the place it appears, where C-u C-x
> = will give information about it.
>
> Select one of the safe coding systems listed below, or cancel the
> writing with C-g and edit the buffer
> to remove or modify the problematic characters,
>
> Regards,
> Janelle
> -----Original Message-----
> From: Philip Kaludercic <philipk@posteo.net>
> Sent: Sunday, September 26, 2021 1:55 PM
> To: Tassilo Horn <tsdh@gnu.org>
> Cc: Janelle Rose <Janelle.T.Rose@frb.gov>; help-gnu-emacs@gnu.org;
> Akber Khan <Akber.Khan@frb.gov>
> Subject: Re: Issues installing packages from melpa
>
>
>
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> It might be some kind of a network issue, but there might be
>> something wrong with the encoding too. Considering the Janelle's
>> domain, I am wondering if there might be a proxy issue.
>
> I just noticed that the first bytes "^_" (hex 1f) and "\213" (hex 8B) are the
> magic bytes for gzip. That means the connection was probably aborted before
> enough data was transmitted for decoding.
--
Philip Kaludercic