Bug#1041767: bug#64829: Leaving .emacs.d/eln-cache on users disks not environmentally sound

tags 64829 notabug wontfix close 64829 thanks > Cc: 1041...@bugs.debian.org > From: Dan Jacobson > Date: Mon, 24 Jul 2023 05:16:04 -0500 > > All I know is based on > > https://emacs.stackexchange.com/questions/71825/how-often-should-emacs-28-1-native-compile-basic-emacs-files > and >

Bug#1021842: Finalizing 'inhibit-automatic-native-compilation'

> From: Andrea Corallo > Cc: monn...@iro.umontreal.ca, t...@debian.org, emacs-de...@gnu.org, > spwhit...@spwhitton.name, 1021...@bugs.debian.org > Date: Mon, 20 Feb 2023 15:42:08 + > > > You mean, from master to emacs-29, I guess? > > Yes > > > What was the motivation for that change?

Bug#1021842: Finalizing 'inhibit-automatic-native-compilation'

> From: Andrea Corallo > Cc: Tatsuya Kinoshita , emacs-de...@gnu.org, > spwhit...@spwhitton.name, 1021...@bugs.debian.org, Eli Zaretskii > > Date: Mon, 20 Feb 2023 09:18:02 + > > Andrea Corallo writes: > > > Stefan Monnier writes: > > > >&

Bug#1021842: Finalizing 'inhibit-automatic-native-compilation'

> From: Andrea Corallo > Cc: Tatsuya Kinoshita , emacs-de...@gnu.org, > spwhit...@spwhitton.name, 1021...@bugs.debian.org, Eli Zaretskii > > Date: Mon, 20 Feb 2023 09:03:34 + > > OTOH on a slightly differnt subject and in light of this, I think we > should proba

Bug#1021842: Finalizing 'inhibit-automatic-native-compilation'

> From: Sean Whitton > Cc: Eli Zaretskii , aymeric.a...@yandex.com, > monn...@iro.umontreal.ca, emacs-de...@gnu.org, la...@gnus.org, > r...@defaultvalue.org > Date: Fri, 17 Feb 2023 09:42:29 -0700 > > > Otherwise you have to revert probably 654428b65ae and 2f28496

Bug#989029: info: prev-line and scroll-backward are buggy on gnuplot.info

> Date: Sat, 12 Nov 2022 13:28:17 +0100 > From: Vincent Lefevre > Cc: gavinsmith0...@gmail.com, bug-texi...@gnu.org, 989...@bugs.debian.org > > > > But "down" is the reverse of "up". > > > > No, it isn't. It is only the reverse of "up" if the node structure is > > a perfect tree. > > But if

Bug#989029: info: prev-line and scroll-backward are buggy on gnuplot.info

> Date: Sat, 12 Nov 2022 12:40:11 +0100 > From: Vincent Lefevre > > > > Oops, I misread the file. I actually think that it is correct. > > > IMHO, to get the tree structure, you should not follow the menu, > > > but only the "File:" lines. > > > > You can't: SPC and DEL are supposed to traverse

Bug#989029: info: prev-line and scroll-backward are buggy on gnuplot.info

> Date: Sat, 12 Nov 2022 11:56:47 +0100 > From: Vincent Lefevre > > Oops, I misread the file. I actually think that it is correct. > IMHO, to get the tree structure, you should not follow the menu, > but only the "File:" lines. You can't: SPC and DEL are supposed to traverse the tree, not just

Bug#989029: info: prev-line and scroll-backward are buggy on gnuplot.info

> Date: Sat, 12 Nov 2022 11:39:41 +0100 > From: Vincent Lefevre > Cc: bug-texi...@gnu.org, 989...@bugs.debian.org > > > * Menu: > > > > * Bugs:: > > > > See that "Bugs" at the end? This is the problem: since "Bugs" is a > > top-level node, its presence in a level-1 node's menu makes the

Bug#989029: info: prev-line and scroll-backward are buggy on gnuplot.info

> Date: Sat, 12 Nov 2022 10:26:39 +0100 > From: Patrice Dumas > Cc: Vincent Lefevre , bug-texi...@gnu.org, > 989...@bugs.debian.org > > On Sat, Nov 12, 2022 at 09:27:34AM +0200, Eli Zaretskii wrote: > > See that "Bugs" at the end? This is the problem: si

Bug#989029: info: prev-line and scroll-backward are buggy on gnuplot.info

> Date: Sat, 12 Nov 2022 00:17:34 +0100 > From: Vincent Lefevre > Cc: 989...@bugs.debian.org > > [Cc to the Debian bug 989029, which I reported last year: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989029 > > I'm now reporting it upstream since it still occurs with "info" > from

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

> Date: Sat, 5 Nov 2022 13:54:54 -0700 > Cc: vinc...@vinc17.net, spwhit...@spwhitton.name, 58...@debbugs.gnu.org, > 1017...@bugs.debian.org > From: Paul Eggert > > On 2022-11-04 00:00, Eli Zaretskii wrote: > > We need to establish what is the > > source of SIGHUP

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

> Date: Sun, 6 Nov 2022 11:44:43 -0800 > Cc: a...@sdf.org, vinc...@vinc17.net, spwhit...@spwhitton.name, > 58...@debbugs.gnu.org, 1017...@bugs.debian.org > From: Paul Eggert > > On 2022-11-06 11:32, Eli Zaretskii wrote: > > My question was whether in this scenario

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

> Date: Sun, 6 Nov 2022 11:18:03 -0800 > Cc: a...@sdf.org, vinc...@vinc17.net, spwhit...@spwhitton.name, > 58...@debbugs.gnu.org, 1017...@bugs.debian.org > From: Paul Eggert > > On 2022-11-05 22:51, Eli Zaretskii wrote: > > > But is it possible for a progr

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

> Date: Sat, 5 Nov 2022 13:54:54 -0700 > Cc: vinc...@vinc17.net, spwhit...@spwhitton.name, 58...@debbugs.gnu.org, > 1017...@bugs.debian.org > From: Paul Eggert > > On 2022-11-04 00:00, Eli Zaretskii wrote: > > We need to establish what is the > > source of SIGHUP

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

> From: Andrea Corallo > Cc: Vincent Lefevre , spwhit...@spwhitton.name, > 58...@debbugs.gnu.org, 1017...@bugs.debian.org > Date: Thu, 03 Nov 2022 21:25:08 + > > AFAIU the Emacs subprocess we use to compile should behave like a > regular Emacs. Basically, you are saying that if the

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

> Date: Thu, 3 Nov 2022 11:13:08 +0100 > From: Vincent Lefevre > Cc: spwhit...@spwhitton.name, 58...@debbugs.gnu.org, > 1017...@bugs.debian.org > > On 2022-11-03 08:47:06 +0200, Eli Zaretskii wrote: > > > On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote: > &

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

> Cc: 58...@debbugs.gnu.org, 1017...@bugs.debian.org > Date: Thu, 3 Nov 2022 04:00:46 +0100 > From: Vincent Lefevre > > On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote: > > Signal 1 is SIGHUP, AFAIU. Why should Emacs receive SIGHUP in the > > middle of GC, I have n

Bug#953033: bug#39901: Emacs needs to update window-width when the user updates the text size

> From: Lars Ingebrigtsen > Date: Wed, 05 Aug 2020 14:04:59 +0200 > Cc: 953...@bugs.debian.org, Katsumi Yamaoka , > 39...@debbugs.gnu.org > > 積丹尼 Dan Jacobson writes: > > > Emacs needs to update window-width when the user updates the text size. > > I think that makes sense. > > Anybody got

Bug#786707: bug#27933: emacs25: default info dir initialization slow with remote filesystems

> From: Glenn Morris <r...@gnu.org> > Cc: Steve McIntyre <st...@einval.com>, 27...@debbugs.gnu.org, > 786...@bugs.debian.org, r...@defaultvalue.org, > 786707-forwar...@bugs.debian.org > Date: Thu, 03 Aug 2017 13:35:25 -0400 > > Eli Zaretskii wrote: > >

Bug#786707: bug#27933: emacs25: default info dir initialization slow with remote filesystems

> Date: Thu, 3 Aug 2017 17:49:13 +0100 > From: Steve McIntyre > Cc: 27...@debbugs.gnu.org, 786...@bugs.debian.org, > Rob Browning , 786707-forwar...@bugs.debian.org > > >2. Why on earth is emacs checking the info path at all on startup? It doesn't

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Sat, 8 Aug 2015 09:00:14 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: Rob Browning r...@defaultvalue.org, 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org One idea I had, which could be useful for Windows and other systems lacking symlinks, is to make an Info file

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Wed, 5 Aug 2015 21:16:36 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: Rob Browning r...@defaultvalue.org, 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org Symlinks are less portable than init files. What operating systems don't support symlinks Windows. (Later

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Tue, 4 Aug 2015 21:20:47 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: Rob Browning r...@defaultvalue.org, 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org A solution that supports inter-manual links, both in Info and in HTML formats. To do this on a per-user

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Wed, 5 Aug 2015 18:09:45 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: Rob Browning r...@defaultvalue.org, 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org Which is why I think having a feature that would transparently replace foo in an Info file name with

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Mon, 3 Aug 2015 21:27:32 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: Rob Browning r...@defaultvalue.org, 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org I don't see how this would solve the issue at hand. Installation of a manual is a system-wide action,

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Tue, 4 Aug 2015 19:51:23 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: Rob Browning r...@defaultvalue.org, 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org On 4 August 2015 at 16:39, Eli Zaretskii e...@gnu.org wrote: You could easily install and access multiple

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Tue, 4 Aug 2015 15:27:51 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: Karl Berry k...@freefriends.org, 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org, Rob Browning r...@defaultvalue.org Suppose there are two emacs installations, one as /usr/bin/emacs, which is

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Tue, 4 Aug 2015 08:10:23 +0900 From: Norbert Preining prein...@logic.at Cc: 793...@bugs.debian.org, bug-texi...@gnu.org, r...@defaultvalue.org lots of mails here, but I still don't see why you are opposing the idea to have different versions of the same program installed, and wanting

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Mon, 3 Aug 2015 23:32:08 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org, Rob Browning r...@defaultvalue.org If you don't care about being able to access renamed files via cross-references, then the renaming of files to

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Tue, 4 Aug 2015 15:16:45 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: Rob Browning r...@defaultvalue.org, 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org On 4 August 2015 at 14:34, Eli Zaretskii e...@gnu.org wrote: It would still be better than what we have

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Tue, 4 Aug 2015 19:55:41 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: Karl Berry k...@freefriends.org, 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org, Rob Browning r...@defaultvalue.org I'm saying that manuals that don't have any executables will be in trouble.

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

From: Rob Browning r...@defaultvalue.org Date: Sun, 02 Aug 2015 18:35:29 -0500 Karl Berry k...@freefriends.org writes: Here's what I don't get: suppose there are two versions of Emacs installed, emacs-x and emacs-y. Presumably Debian (and anyone else) has some method for the user to

Bug#793067: Bug#792328: info: can no longer find the Emacs manual

Date: Mon, 3 Aug 2015 15:16:27 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: 793...@bugs.debian.org, Texinfo bug-texi...@gnu.org On 3 August 2015 at 14:22, Gavin Smith gavinsmith0...@gmail.com wrote: I'm wondering if we can kill two birds with one stone here and get install-info

Bug#792328: info: can no longer find the Emacs manual

Date: Wed, 15 Jul 2015 20:08:47 +0200 From: Vincent Lefevre vinc...@vinc17.net Cc: Norbert Preining norb...@preining.info, gavinsmith0...@gmail.com, 792...@bugs.debian.org, bug-texi...@gnu.org Then one could do info emacs-24::emacs etc? Please don't make characters

Bug#792328: info: can no longer find the Emacs manual

Date: Wed, 15 Jul 2015 23:06:03 +0900 From: Norbert Preining norb...@preining.info Cc: 792...@bugs.debian.org, Vincent Lefevre vinc...@vinc17.net, Texinfo bug-texi...@gnu.org What about encoding sub-dirs in the dir file with'::' like: * Emacs: (emacs-24::emacs). The

Bug#792328: (fwd) Bug#792328: info: can no longer find the Emacs manual

Date: Wed, 15 Jul 2015 12:14:41 +0100 From: Gavin Smith gavinsmith0...@gmail.com Cc: 792...@bugs.debian.org, Vincent Lefevre vinc...@vinc17.net, Texinfo bug-texi...@gnu.org down here at Debian a certain inconvenience has arrived: Namely that info cannot follow links to info files

Bug#755351: bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default

Date: Mon, 1 Sep 2014 11:24:31 -0700 From: Josh Triplett j...@joshtriplett.org Cc: 755...@bugs.debian.org, Rob Browning r...@defaultvalue.org, 18...@debbugs.gnu.org, 755351-forwar...@bugs.debian.org For the simplest possible implementation, determine the desktop setting for whether

Bug#696026: bug#13505: Bug#696026: emacs24: file corruption on saving

Date: Tue, 22 Jan 2013 03:35:57 +0100 From: Vincent Lefevre vinc...@vinc17.net Cc: r...@defaultvalue.org, ha...@gnu.org, 13...@debbugs.gnu.org, 696026-forwar...@bugs.debian.org, 696...@bugs.debian.org | The original encoded form of the characters as found on disk at | visit

Bug#696026: bug#13505: Bug#696026: emacs24: file corruption on saving

Date: Mon, 21 Jan 2013 05:14:10 +0100 From: Vincent Lefevre vinc...@vinc17.net Cc: r...@defaultvalue.org, ha...@gnu.org, 13...@debbugs.gnu.org, 696026-forwar...@bugs.debian.org, 696...@bugs.debian.org On 2013-01-21 05:48:14 +0200, Eli Zaretskii wrote: You said

Bug#696026: bug#13505: Bug#696026: emacs24: file corruption on saving

From: Rob Browning r...@defaultvalue.org Date: Sat, 19 Jan 2013 22:09:28 -0600 Cc: 696026-forwar...@bugs.debian.org, Vincent Lefevre vinc...@vinc17.net, 696...@bugs.debian.org Vincent Lefevre vinc...@vinc17.net writes: Package: emacs24 Version: 24.2+1-1 Severity: grave

Bug#696026: bug#13505: Bug#696026: emacs24: file corruption on saving

Date: Sun, 20 Jan 2013 22:25:08 +0100 From: Vincent Lefevre vinc...@vinc17.net Cc: Rob Browning r...@defaultvalue.org, Kenichi Handa ha...@gnu.org, 13...@debbugs.gnu.org, 696026-forwar...@bugs.debian.org, 696...@bugs.debian.org On 2013-01-20 18:49:38 +0200, Eli Zaretskii wrote

Bug#696026: bug#13505: Bug#696026: emacs24: file corruption on saving

Date: Sun, 20 Jan 2013 23:10:08 +0100 From: Vincent Lefevre vinc...@vinc17.net Cc: r...@defaultvalue.org, ha...@gnu.org, 13...@debbugs.gnu.org, 696026-forwar...@bugs.debian.org, 696...@bugs.debian.org On 2013-01-20 23:40:14 +0200, Eli Zaretskii wrote: Date: Sun, 20 Jan 2013 22:25

Bug#696026: bug#13505: Bug#696026: emacs24: file corruption on saving

Date: Sun, 20 Jan 2013 23:22:11 +0100 From: Vincent Lefevre vinc...@vinc17.net Cc: r...@defaultvalue.org, ha...@gnu.org, 13...@debbugs.gnu.org, 696026-forwar...@bugs.debian.org, 696...@bugs.debian.org On 2013-01-20 23:10:08 +0100, Vincent Lefevre wrote: But Emacs should clearly tell

Bug#655118: bug#10592: Bug#655118: Please enabled hardened build flags

From: Rob Browning r...@defaultvalue.org Cc: 10...@debbugs.gnu.org, 655...@bugs.debian.org, 655118-forwar...@bugs.debian.org, j...@inutil.org Date: Tue, 24 Jan 2012 20:22:52 -0600 Eli Zaretskii e...@gnu.org writes: I think the right fix for this is to declare `error

Bug#655118: bug#10592: Bug#655118: Please enabled hardened build flags

From: Rob Browning r...@defaultvalue.org Date: Mon, 23 Jan 2012 23:05:26 -0600 Cc: 655...@bugs.debian.org, 655118-forwar...@bugs.debian.org, Moritz Mühlenhoff j...@inutil.org --- emacs23-23.3+1.orig/lib-src/movemail.c2011-12-29 05:07:27.0 +0100 +++

Bug#620795: bug#8497: Bug#620795: emacs23: Makefile generation with cpp mangles multiarch include paths (impending FTBFS)

From: Rob Browning r...@defaultvalue.org Date: Wed, 13 Apr 2011 22:56:03 -0500 Cc: 620795-forwar...@bugs.debian.org, Steve Langasek steve.langa...@canonical.com, 620...@bugs.debian.org (If possible, please preserve the 620795-forwarded address in any replies.) Debian is likely to

Bug#608023: bug#7732: Bug#608023: ispell-buffer always gives bogus (0) and (1) choices

From: jida...@jidanni.org Date: Sun, 26 Dec 2010 12:09:35 +0800 Resent-Sender: Debian BTS debb...@busoni.debian.org Cc: EZ do a type ispell, perhaps there are more surprises there. $ type ispell ispell is hashed (/usr/bin/ispell) And what does file /usr/bin/ispell say? -- To

Bug#608023: bug#7732: Bug#608023: ispell-buffer always gives bogus (0) and (1) choices

From: jida...@jidanni.org Cc: 608...@bugs.debian.org Date: Mon, 27 Dec 2010 08:32:48 +0800 EZ == Eli Zaretskii e...@gnu.org writes: EZ And what does file /usr/bin/ispell say? /usr/bin/ispell: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs

Bug#374513: emacs-snapshot: Info dir hidden words obscure versions

From: Dan Jacobson [EMAIL PROTECTED] Date: Mon, 19 Jun 2006 22:51:17 +0800 Gentlemen, (here on Debian, emacs-version 22.0.50.1) do C-h i M-x occur gnus: 4 matches for gnus in buffer: *info* 242:* Gnus: (emacs-21/gnus). The newsreader Gnus. 247:

Bug#234848: Bug reports for texinfo (and 2 wishes)

Date: Mon, 13 Feb 2006 18:27:38 -0600 From: [EMAIL PROTECTED] (Karl Berry) Cc: [EMAIL PROTECTED], bug-texinfo@gnu.org (Is it just me, or is this code really hard to follow?) It's not just you. ;-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble?

Bug#234848: Bug reports for texinfo (and 2 wishes)

Date: Sat, 11 Feb 2006 18:36:22 -0600 From: [EMAIL PROTECTED] (Karl Berry) Cc: [EMAIL PROTECTED], bug-texinfo@gnu.org Does your info also go to make_manpage_node and returns a if (node) true? I take it back. I fixed my man setup but make_manpage_node still returns zero. Not

Bug#146133: info goto node with dot

Date: Fri, 27 Jan 2006 23:16:15 +0100 From: Norbert Preining [EMAIL PROTECTED] Cc: bug-texinfo@gnu.org, [EMAIL PROTECTED] Ahh, bingo... I found the problem. It is really a parsing, and only in the case when . That's because this string can end a node name in a menu. See Karl's