From: Waleed Yousef <wyousef@fcih.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55553@debbugs.gnu.org
Subject: bug#55553: 28.1; Forward and Reply does not incude message
Date: Thu, 26 May 2022 13:46:16 -0700 [thread overview]
Message-ID: <C8B01E83-B1B4-4F01-9A8A-A3BB5E0E6CD2@fcih.net> (raw)
In-Reply-To: <87wne89hm8.fsf@gnus.org>
I am using spacemacs. I did not define more packages than the default
> On May 26, 2022, at 1:14 PM, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Waleed Yousef <wyousef@fcih.net> writes:
>
>> In addition to my last reply (which I even cannot find it in the sent
>> messages, which is another anomaly that started occurring
>> simultaneously with the problem that I reported) an additional
>> information that may help is this. The same problem happens when, e.g.,
>> I start editing a message, then save it, then go to "drafts" to open it
>> using `e`. This starts a new empty message, and does not open the saved message!
>
> It sounds like you're using a bunch of packages/customisations that's
> redefining key bindings. Try removing those.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-26 20:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 1:32 bug#55553: 28.1; Forward and Reply does not incude message Waleed Yousef
2022-05-21 13:41 ` Lars Ingebrigtsen
2022-05-22 2:14 ` Waleed Yousef
2022-05-22 6:22 ` Pankaj Jangid
2022-05-26 20:09 ` Waleed Yousef
2022-05-26 20:14 ` Lars Ingebrigtsen
2022-05-26 20:46 ` Waleed Yousef [this message]
2022-05-27 10:35 ` Lars Ingebrigtsen
2022-05-28 1:48 ` Waleed Yousef
2022-05-28 6:19 ` Eli Zaretskii
2022-05-28 8:23 ` Waleed Yousef
2022-05-28 9:30 ` Eli Zaretskii
2022-05-31 0:07 ` Waleed Yousef
2022-05-31 18:37 ` Lars Ingebrigtsen
2022-06-29 10:24 ` Lars Ingebrigtsen
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=C8B01E83-B1B4-4F01-9A8A-A3BB5E0E6CD2@fcih.net \
--to=wyousef@fcih.net \
--cc=55553@debbugs.gnu.org \
--cc=larsi@gnus.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.