unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: 49426@debbugs.gnu.org
Cc: Stefan Kangas <stefan@marxist.se>
Subject: bug#49426: 28.0.50; Byte-compilation can fail with large fill-column
Date: Tue, 06 Jul 2021 09:07:32 +0100	[thread overview]
Message-ID: <87a6mzsw57.fsf@tcd.ie> (raw)
In-Reply-To: <87r1gc2t53.fsf@tcd.ie> (Basil L. Contovounesios's message of "Tue, 06 Jul 2021 01:16:56 +0100")

"Basil L. Contovounesios" <contovob@tcd.ie> writes:

> The same error occurs post-installation with 'M-x byte-compile-file' on
> dash.el.  Either way, the error confusingly only shows up when Dash is
> installed from MELPA:
>
>   package-archives = '(("melpa" . "https://melpa.org/packages/"))
>
> and not from GNU-devel ELPA:
>
>   package-archives = '(("gnu" . "https://elpa.gnu.org/devel/"))
>
> even though both contain identical versions of the file dash.el.  So I
> guess it's some other part of the package .tar that gives rise to the
> discrepancy.

Duh, the GNU ELPA .tar includes a .dir-locals.el with a custom
fill-column, whereas the MELPA package installs only dash.el and its
Texinfo manual, so there is nothing to override the pathological default
value of fill-column.

In which case the recipe becomes much simpler:

0. emacs -Q
1. M-: (setq-default fill-column 9999999) RET
2. (defalias 'foo #'ignore "Foo.")
3. C-x C-s foo.el RET
4. M-x byte-compile-file RET foo.el RET

This gives:

Compiling file /home/blc/foo.el at Tue Jul  6 09:05:44 2021
foo.el:4:1: Error: Invalid regexp: "Invalid content of \\{\\}"

-- 
Basil





  reply	other threads:[~2021-07-06  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06  0:16 bug#49426: 28.0.50; Byte-compilation can fail with large fill-column Basil L. Contovounesios
2021-07-06  8:07 ` Basil L. Contovounesios [this message]
2021-07-06 15:08 ` Lars Ingebrigtsen
2021-07-06 18:14   ` Basil L. Contovounesios

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=87a6mzsw57.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=49426@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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).