From: "T.V Raman" <raman@google.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Pankaj Jangid <pankaj@codeisgreat.org>, emacs-devel@gnu.org
Subject: Re: Hunting the culprit package
Date: Wed, 31 Aug 2022 17:31:24 -0700 [thread overview]
Message-ID: <p914jxsj5pf.fsf@google.com> (raw)
In-Reply-To: <jwva67khxr3.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 31 Aug 2022 18:12:03 -0400")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1046 bytes --]
Stefan Monnier <monnier@iro.umontreal.ca> writes:
I disagreethat we were not a "resounding" success;
1. We were successful as you pointed out.
2. We were still making noise -- so that meets the "resounding" bar.
>> Because magit is hooked into so many places, every part of Emacs was
>> giving some error. For example, pressing RET on an info node was also
>> not working.
>>
>> An external package can cause so much damage. Can this be prevented?
>
> :-)
>
> Emacs tries to make a lot of things possible. It also tries to prevent
> bad things, but it tends to be pretty conservative in this respect since
> the two goals are in conflict.
>
> To the extent that your problem prevented you from using Emacs but
> did not make you lose work (presumably), then I'd consider that the
> efforts we make to "prevent bad things" were successful.
> Maybe not a resounding success, admittedly.
>
>
> Stefan
>
>
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2022-09-01 0:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 5:41 Hunting the culprit package Pankaj Jangid
2022-08-31 12:25 ` Stefan Monnier
2022-08-31 17:20 ` Pankaj Jangid
2022-08-31 22:12 ` Stefan Monnier
2022-09-01 0:31 ` T.V Raman [this message]
2022-09-03 2:51 ` Magit Richard Stallman
2022-09-03 6:29 ` Magit Akib Azmain Turja
2022-09-03 14:20 ` Magit Stefan Monnier
2022-09-03 14:56 ` Magit Eli Zaretskii
2022-09-03 18:22 ` Magit Akib Azmain Turja
2022-09-03 18:34 ` Magit Eli Zaretskii
2022-09-04 2:47 ` Magit Akib Azmain Turja
2022-09-04 5:16 ` Magit Eli Zaretskii
2022-09-03 15:16 ` Magit Stefan Kangas
2022-09-03 18:32 ` Magit Akib Azmain Turja
2022-09-03 18:51 ` Magit broken in NonGNU ELPA Stefan Kangas
2022-09-03 19:09 ` Magit Philip Kaludercic
2022-09-05 4:03 ` Magit Richard Stallman
2022-09-05 8:58 ` Magit Philip Kaludercic
2022-09-07 2:19 ` Magit Richard Stallman
2022-09-07 3:33 ` Magit Phil Sainty
2022-09-07 12:40 ` Magit Stefan Monnier
2022-09-07 13:02 ` Magit Akib Azmain Turja
2022-09-03 18:45 ` Magit Stefan Monnier
2022-09-05 4:03 ` Magit Richard Stallman
2022-09-05 9:04 ` Magit Philip Kaludercic
2022-09-05 11:48 ` Magit Eli Zaretskii
2022-09-07 2:19 ` Magit Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p914jxsj5pf.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pankaj@codeisgreat.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.