From: Philip Kaludercic <philipk@posteo.net>
To: "Johann Klähn" <johann@jklaehn.de>
Cc: Stefan Kangas <stefankangas@gmail.com>,
Tassilo Horn <tsdh@gnu.org>,
emacs-devel@gnu.org
Subject: Re: [NonGNU ELPA] New package: eldoc-diffstat
Date: Sun, 15 Dec 2024 10:11:42 +0000 [thread overview]
Message-ID: <87o71ds1b5.fsf@posteo.net> (raw)
In-Reply-To: <87cyhuaqun.fsf@jklaehn.de> ("Johann Klähn"'s message of "Sat, 14 Dec 2024 22:37:20 +0100")
Johann Klähn <johann@jklaehn.de> writes:
> Thanks for your comments, everyone!
[...]
> On Sat, Dec 14, 2024 at 10:11 +0000, Philip Kaludercic wrote:
>> '((Git "git" "--no-pager" "show" "--color=always"
>> - "--format=format:%an <%ae>, %aD:%n%s" "--stat=80")
>> + "--format=format:%an <%ae>, %aD:%n%s" "--stat=80")
>
> Some lines look like spurious whitespace changes? I hope I picked out
> all functional changes.
That is true, my apologies.
>> + ;; Is it an issue that there is the slight possibility of a race
>> + ;; condition here?
>
> I happened to have the same thought yesterday, also w.r.t. the
> sentinel function.
As far as I see, there is no way of avoiding this without extending
`make-process' to accept a process plist (which wouldn't be backwards
compatible). But if you don't insist on using the process plist, you
could capture the revision info in a closure and pass it on to the
sentinel.
>> The rewriting of
>> `eldoc-diffstat--format-output-buffer' might be controversial, but I
>> feel that using a regular expression to destruct the buffer feels more
>> robust.
>
> Yes, probably. Though I decided to keep the original output if the
> regex fails to match, as it might help users figure out what's happening.
That's fine as well of course!
next prev parent reply other threads:[~2024-12-15 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 20:31 [NonGNU ELPA] New package: eldoc-diffstat Johann Klähn
2024-12-13 20:23 ` Tassilo Horn
2024-12-14 13:24 ` Stefan Kangas
2024-12-14 21:37 ` Johann Klähn
2024-12-15 0:38 ` Stefan Kangas
2024-12-15 10:11 ` Philip Kaludercic [this message]
2024-12-14 10:11 ` Philip Kaludercic
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o71ds1b5.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=johann@jklaehn.de \
--cc=stefankangas@gmail.com \
--cc=tsdh@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).