From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31988@debbugs.gnu.org
Subject: bug#31988: scroll-other-window broken on master
Date: Sat, 07 Jul 2018 17:14:29 +0300 [thread overview]
Message-ID: <874lhb16be.fsf@tcd.ie> (raw)
In-Reply-To: <83wou7i288.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 7 Jul 2018 16:50:47 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>> Cc: Daniel Colascione <dancol@dancol.org>, <31988@debbugs.gnu.org>,
>> <31988-done@debbugs.gnu.org>
>> Date: Sat, 07 Jul 2018 16:40:17 +0300
>>
>> I don't yet feel particularly good at or confident with writing
>> changelog entries, let alone Emacs C code, so any guidance is more than
>> welcome now and in the future.
>
> I think you are doing just fine, thank you. There's always some
> learning curve, of course. CONTRIBUTE should tell you enough, and you
> can study the log messages by veterans to pick up the spirit.
>
> The "inaccurate" part in my message related not to your wording (which
> was fine, AFAICT), but to the fact that the important part of your fix
> was to call save-excursion in the described case, not the part that
> set the buffer (which was actually a no-op).
>
>> I'm not sure whether Daniel's addition of the 'close' tag had the
>> intended effect
>
> It should have, but it looks like it didn't for some reason.
>
>> so I'm taking the liberty of CCing <31988-done@debbugs.gnu.org>; if
>> this was the wrong thing to do, please let me know what I should
>> have done instead.
>
> Doing that for a bug that should be closed can never do any harm, even
> if it was already closed. (You also don't need to CC both NNN@ and
> NNN-done@, as the message gets recorded by the tracker even if you
> only use the latter.)
Thanks for explaining everything, it all makes sense.
--
Basil
prev parent reply other threads:[~2018-07-07 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 19:54 bug#31988: scroll-other-window broken on master Daniel Colascione
2018-06-27 20:44 ` Daniel Colascione
2018-06-27 21:26 ` Basil L. Contovounesios
2018-07-06 15:18 ` Daniel Colascione
2018-07-06 22:20 ` Basil L. Contovounesios
2018-07-06 23:31 ` Daniel Colascione
2018-07-07 7:48 ` Eli Zaretskii
2018-07-07 13:40 ` Basil L. Contovounesios
2018-07-07 13:50 ` Eli Zaretskii
2018-07-07 14:14 ` Basil L. Contovounesios [this message]
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=874lhb16be.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=31988@debbugs.gnu.org \
--cc=eliz@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).