GNU bug report logs - #74339
30.0.92; CC Mode stomps C TS Mode

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: acm <at> muc.de, monnier <at> iro.umontreal.ca, 74339 <at> debbugs.gnu.org
Subject: bug#74339: 30.0.92; CC Mode stomps C TS Mode
Date: Sat, 16 Nov 2024 16:35:36 +0200

> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Sat, 16 Nov 2024 06:03:14 -0800
> Cc: acm <at> muc.de, 74339 <at> debbugs.gnu.org
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> >> Cc: Eli Zaretskii <eliz <at> gnu.org>,  74339 <at> debbugs.gnu.org
> >> Date: Fri, 15 Nov 2024 15:45:46 -0500
> >>
> >> > Here it is evident that by "mode:c" the OP means C Mode, not whatever
> >> > random mode happens to have taken the symbol `c-mode'.
> >>
> >> It is evident that the OP means CC-mode's C Mode because the bug report
> >> is sent to `bug-cc-mode`, indeed.
> >
> > Perhaps we should introduce (on master) a boolean variable to disable
> > mode remapping?  Then files which want to force a mode could specify
> > that.
> 
> I'm not sure what is the use case for something like that.
> Do we want files to be able to override user preferences?

The case of CC Mode bug report above might be one such example.

A (hypothetical) tutorial for using CC Mode (e.g., teaching about its
interactive indentation customization feature) might be another.

It isn't supposed to be a frequent situation, but when it happens, why
not allow it to be supported?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.