all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ruijie@netyu.xyz, 63472@debbugs.gnu.org, kristofer.hjelmtorp@mailbox.org
Subject: bug#63472: 30.0.50; internal-border-width > 0 "eats" tab-bar for Emacs --pgtk
Date: Sat, 13 May 2023 16:13:52 +0800	[thread overview]
Message-ID: <87fs807inz.fsf@yahoo.com> (raw)
In-Reply-To: <831qjkbud5.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 13 May 2023 09:47:34 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Thanks, but please in the future try to avoid reformatting the source
> code (like you did in dispnew.c): it makes the forensics harder,
> especially in files that are too large for "git log -L" to work.
>
> TIA

Sorry, that was a mistake.  I undid a code change there but not the
formatting.





  reply	other threads:[~2023-05-13  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 18:38 bug#63472: 30.0.50; internal-border-width > 0 "eats" tab-bar for Emacs --pgtk Kristofer Hjelmtorp via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-13  2:19 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-13  2:28   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-13  6:47     ` Eli Zaretskii
2023-05-13  8:13       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-05-18 18:47     ` Kristofer Hjelmtorp via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-19  0:52       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-13  6:44   ` Eli Zaretskii

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=87fs807inz.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=63472@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kristofer.hjelmtorp@mailbox.org \
    --cc=luangruo@yahoo.com \
    --cc=ruijie@netyu.xyz \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.