From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: coding in some mails is wired
Date: Thu, 27 Jul 2023 09:15:07 +0200 [thread overview]
Message-ID: <874jlpkepw.fsf@gmail.com> (raw)
In-Reply-To: <87edkusj5c.fsf@mat.ucm.es>
>>>>> On Wed, 26 Jul 2023 18:59:59 +0200, Uwe Brauer <oub@mat.ucm.es> said:
>> Which version of Emacs are you using?
Uwe> emacs-repository-version is a variable defined in ‘version.el’.
Uwe> Its value is "7bf17ceee8c2d347917541e143ce25609e90ebbb"
Thatʼs pretty old. Any chance you could try with a more recent
version?
Robert
--
next prev parent reply other threads:[~2023-07-27 7:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 7:49 Uwe Brauer
2023-07-25 9:57 ` Robert Pluim
2023-07-25 12:28 ` Uwe Brauer
2023-07-25 13:24 ` Robert Pluim
2023-07-25 17:46 ` Uwe Brauer
2023-07-25 20:49 ` Robert Pluim
2023-07-26 9:03 ` Uwe Brauer
2023-07-26 9:19 ` Eric S Fraga
2023-07-26 10:07 ` Robert Pluim
2023-07-26 10:21 ` Eric S Fraga
2023-07-26 12:16 ` Uwe Brauer
2023-07-26 12:58 ` Robert Pluim
2023-07-26 16:59 ` Uwe Brauer
2023-07-27 7:15 ` Robert Pluim [this message]
2023-07-29 5:55 ` Uwe Brauer
2023-07-25 16:21 ` Andreas Schwab
2023-07-25 17:46 ` Uwe Brauer
2023-07-25 17:50 ` Uwe Brauer
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=874jlpkepw.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=ding@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.
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 NNTP newsgroup(s).