GNU bug report logs -
#59602
29.0.50; csharp-mode should either be a package, or compat code could be removed
Previous Next
Reported by: Stefan Kangas <stefankangas <at> gmail.com>
Date: Sat, 26 Nov 2022 08:15:01 UTC
Severity: wishlist
Tags: patch
Found in version 29.0.50
Done: Stefan Kangas <stefankangas <at> gmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 59602 in the body.
You can then email your comments to 59602 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
theo <at> thornhill.no, jostein <at> kjonigsen.net, bug-gnu-emacs <at> gnu.org
:
bug#59602
; Package
emacs
.
(Sat, 26 Nov 2022 08:15:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Stefan Kangas <stefankangas <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
theo <at> thornhill.no, jostein <at> kjonigsen.net, bug-gnu-emacs <at> gnu.org
.
(Sat, 26 Nov 2022 08:15:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Severity: wishlist
Is csharp-mode.el intended to be a :core package or should people just
use the version that comes with Emacs?
If the former, I guess some Version and Package-Requires headers
are needed.
If the latter, the compat code starting on line 512 could probably be
removed.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#59602
; Package
emacs
.
(Sat, 26 Nov 2022 19:14:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 59602 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Stefan Kangas <stefankangas <at> gmail.com> writes:
> Severity: wishlist
>
> Is csharp-mode.el intended to be a :core package or should people just
> use the version that comes with Emacs?
>
> If the former, I guess some Version and Package-Requires headers
> are needed.
>
> If the latter, the compat code starting on line 512 could probably be
> removed.
I agree. The compat code should be removed. I don't thing we have much
to gain by maintaining this as a :core package, so here's a patch doing
what you suggest. I don't think that code should be part of Emacs at
all, if not absolutely necessary :-)
Theo
[0001-Remove-compatibility-code-in-csharp-mode.patch (text/x-diff, attachment)]
Added tag(s) patch.
Request was from
Stefan Kangas <stefankangas <at> gmail.com>
to
control <at> debbugs.gnu.org
.
(Sat, 26 Nov 2022 19:26:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#59602
; Package
emacs
.
(Sat, 26 Nov 2022 20:59:01 GMT)
Full text and
rfc822 format available.
Message #13 received at 59602 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
This may be a bit "on the side", but if me and Theodor are going to be
maintaining csharp-mode in Emacs core, we currently face the slight
"challenge" of not actually having write/push-access to the Emacs
git-repo at savannah.
That means that at top of our ability, we will be able to email in
patches (like Theodor did now!) and hope for someone to review and/or
merge them.
While don't expect that providing for unlimited git-access out of the
blue probably is how new major-modes are taken in, I'm also not sure
what the "normal" procedure is in cases like this.
Are there someone particular we are recommended to CC in our emails to
make sure the patches get picked up efficiently? And what if it's not a
registered "bug" yet, but just an improvement? Should we send it to
emacs-devel instead?
In short: Do you guys have any "onboarding guide" we can follow to make
sure everyone is happy, and our patches get reviewed and applied
efficiently? :)
Any guidance appreciated!
--
Kind regards
*Jostein Kjønigsen*
jostein <at> kjonigsen.net 🍵 jostein <at> gmail.com
https://jostein.kjønigsen.no <https://jostein.kjønigsen.no>
On 26.11.2022 20:12, Theodor Thornhill wrote:
> Stefan Kangas<stefankangas <at> gmail.com> writes:
>
>> Severity: wishlist
>>
>> Is csharp-mode.el intended to be a :core package or should people just
>> use the version that comes with Emacs?
>>
>> If the former, I guess some Version and Package-Requires headers
>> are needed.
>>
>> If the latter, the compat code starting on line 512 could probably be
>> removed.
> I agree. The compat code should be removed. I don't thing we have much
> to gain by maintaining this as a :core package, so here's a patch doing
> what you suggest. I don't think that code should be part of Emacs at
> all, if not absolutely necessary :-)
>
> Theo
>
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#59602
; Package
emacs
.
(Sun, 27 Nov 2022 06:04:01 GMT)
Full text and
rfc822 format available.
Message #16 received at 59602 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 26 Nov 2022 21:58:35 +0100
> From: Jostein Kjønigsen <jostein <at> secure.kjonigsen.net>
>
> While don't expect that providing for unlimited git-access out of the blue probably is how new major-modes
> are taken in, I'm also not sure what the "normal" procedure is in cases like this.
The "normal" procedure is to keep posting patches for review until you feel
you've been doing that long enough, and managed to get to the state where
your patches get only minor review comments, especially about coding and
documentation conventions. Then request write access.
> Are there someone particular we are recommended to CC in our emails to make sure the patches get
> picked up efficiently? And what if it's not a registered "bug" yet, but just an improvement? Should we send it
> to emacs-devel instead?
It is always best to use report-emacs-bug for sending patches, even if it
isn't a bug. debbugs is our issue tracker, not just bug tracker.
emacs-devel is for discussing ideas and asking questions (you can also post
diffs to better explain what you mean or if the question is about a
particular code).
TIA
Reply sent
to
Stefan Kangas <stefankangas <at> gmail.com>
:
You have taken responsibility.
(Sun, 27 Nov 2022 09:39:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Stefan Kangas <stefankangas <at> gmail.com>
:
bug acknowledged by developer.
(Sun, 27 Nov 2022 09:39:03 GMT)
Full text and
rfc822 format available.
Message #21 received at 59602-done <at> debbugs.gnu.org (full text, mbox):
Theodor Thornhill <theo <at> thornhill.no> writes:
> I agree. The compat code should be removed. I don't thing we have much
> to gain by maintaining this as a :core package, so here's a patch doing
> what you suggest. I don't think that code should be part of Emacs at
> all, if not absolutely necessary :-)
Thanks, since both you and Jostein seems to agree, I've pushed this
change (commit ea2f2f1e71). I'm therefore closing this bug report.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#59602
; Package
emacs
.
(Sun, 27 Nov 2022 10:00:02 GMT)
Full text and
rfc822 format available.
Message #24 received at 59602-done <at> debbugs.gnu.org (full text, mbox):
On 27 November 2022 10:38:44 CET, Stefan Kangas <stefankangas <at> gmail.com> wrote:
>Theodor Thornhill <theo <at> thornhill.no> writes:
>
>> I agree. The compat code should be removed. I don't thing we have much
>> to gain by maintaining this as a :core package, so here's a patch doing
>> what you suggest. I don't think that code should be part of Emacs at
>> all, if not absolutely necessary :-)
>
>Thanks, since both you and Jostein seems to agree, I've pushed this
>change (commit ea2f2f1e71). I'm therefore closing this bug report.
Thanks, appreciate it :)
Theo
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 25 Dec 2022 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 175 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.