From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: "55443@debbugs.gnu.org" <55443@debbugs.gnu.org>
Subject: bug#55443: [PATCH] gnu: emacs: Fix source snippet.
Date: Thu, 23 Jun 2022 07:26:55 +0200 [thread overview]
Message-ID: <8b411d7cab5f227874211fcc9281b4512cf577f1.camel@gmail.com> (raw)
In-Reply-To: <AkfejsQnw1AQkIxpB9Y8k8SniicNxAOsaVEuxMsQSST_xrpm6kAUTvWN0JqsMBZI4LAsYPwjl2tkC1ZNkpRACS5oD7Nhfedx0bwCoGcjnlA=@protonmail.com>
Am Mittwoch, dem 22.06.2022 um 20:06 +0000 schrieb John Kehayias:
> [...]
> On Wednesday, June 22nd, 2022 at 3:47 PM, Liliana Marie Prikler
> wrote:
> > [O]ur tramp fixes should at some point also end up in the actual
> > tramp package, not just emacs itself :)
> [...]
> And yes, we should see about getting this in emacs proper, they
> should have GNU's own Guix taken care of as well :)
Actually, the point was to also have them in our emacs-tramp package,
which (like emacs-org) doesn't always receive the fixups that land in
the emacs package. Lots of work duplicated since Emacs vendors those.
Cheers
next prev parent reply other threads:[~2022-06-23 5:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 6:27 bug#55443: emacs-28.1: tramp sudo broken Remco van 't Veer
2022-05-19 12:46 ` benoit
2022-05-19 13:57 ` Josselin Poiret via Bug reports for GNU Guix
2022-05-19 14:55 ` Remco van 't Veer
2022-06-22 1:53 ` bug#55443: [PATCH] gnu: emacs: Fix source snippet John Kehayias via Bug reports for GNU Guix
2022-06-22 14:41 ` John Kehayias via Bug reports for GNU Guix
2022-06-22 19:47 ` Liliana Marie Prikler
2022-06-22 20:06 ` John Kehayias via Bug reports for GNU Guix
2022-06-23 5:26 ` Liliana Marie Prikler [this message]
[not found] ` <handler.55443.D55443.165592726026934.notifdone@debbugs.gnu.org>
2022-06-25 14:57 ` bug#55443: closed (Re: [PATCH] gnu: emacs: Fix source snippet.) Remco van 't Veer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b411d7cab5f227874211fcc9281b4512cf577f1.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=55443@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).