unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: master 5df658a96a: Fix handling of intspecs as string by rcirc-define-command
Date: Tue, 19 Apr 2022 20:31:52 +0800	[thread overview]
Message-ID: <87ilr5dzk7.fsf@yahoo.com> (raw)
In-Reply-To: <87o80xmgw6.fsf@posteo.net> (Philip Kaludercic's message of "Tue,  19 Apr 2022 11:50:17 +0000")

Philip Kaludercic <philipk@posteo.net> writes:

> Po Lu <luangruo@yahoo.com> writes:
>
>> Philip Kaludercic <philipk@posteo.net> writes:
>>
>>> Am I missing something or do you just mean to say that it was supposed
>>> to be "lisp/net/rcirc.el" instead of "rcirc.el"?
>>
>> That, and the lines shouldn't start with a space either.
>
> Oh, I see.  I will pay more attention to that in the future, but in my
> defence, both of these things appear to be the default behaviour.
> log-edit-generate-changelog-from-diff only uses the basename of the file
> (though I have proposed to change that in <87pmqhl85r.fsf@posteo.net>),
> and auto-fill-mode inserts the leading whitespace, apparently because it
> assumes that the changelog is a plaintext list.

I don't use auto-fill-mode, and don't see that behavior when filling the
text manually.



  reply	other threads:[~2022-04-19 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <165036713452.19237.1130079565723437473@vcs2.savannah.gnu.org>
     [not found] ` <20220419111854.C50E3C009A8@vcs2.savannah.gnu.org>
2022-04-19 11:27   ` master 5df658a96a: Fix handling of intspecs as string by rcirc-define-command Po Lu
2022-04-19 11:32     ` Philip Kaludercic
2022-04-19 11:45       ` Po Lu
2022-04-19 11:50         ` Philip Kaludercic
2022-04-19 12:31           ` Po Lu [this message]
2022-04-19 14:13             ` 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=87ilr5dzk7.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /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).