all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 35596-done@debbugs.gnu.org, juri@linkov.net
Subject: bug#35596: view-lossage should leave less blank lines at bottom
Date: Wed, 08 May 2019 15:31:57 +0300	[thread overview]
Message-ID: <8336lpi0ua.fsf@gnu.org> (raw)
In-Reply-To: <87ef59b233.5.fsf@jidanni.org> (message from 積丹尼 Dan Jacobson on Wed, 08 May 2019 19:46:56 +0800)

> From: 積丹尼 Dan Jacobson <jidanni@jidanni.org>
> Cc: juri@linkov.net,  35596@debbugs.gnu.org
> Date: Wed, 08 May 2019 19:46:56 +0800
> 
> I think there shouldn't be any blank lines following the "\n[back]",
> unless we just started emacs and there isn't much to report.
> 
> I think this should be the default behavior and users shouldn't need to
> set some variable (that is not even mentioned on C-h k C-h l) to "some
> value over 100" to achieve it.

And I think there's nothing wrong with the default behavior as it is.
Emacs behaves like that with any window that pops up to show any
content.





  reply	other threads:[~2019-05-08 12:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06  0:24 bug#35596: view-lossage should leave less blank lines at bottom 積丹尼 Dan Jacobson
2019-05-07 20:27 ` Juri Linkov
2019-05-07 21:45   ` 積丹尼 Dan Jacobson
2019-05-08  5:59     ` Eli Zaretskii
2019-05-08  6:42       ` 積丹尼 Dan Jacobson
2019-05-08  7:05         ` Eli Zaretskii
2019-05-08  7:21           ` 積丹尼 Dan Jacobson
2019-05-08  7:59             ` Eli Zaretskii
2019-05-08  8:05               ` 積丹尼 Dan Jacobson
2019-05-08  8:44                 ` Eli Zaretskii
2019-05-08 11:46                   ` 積丹尼 Dan Jacobson
2019-05-08 12:31                     ` Eli Zaretskii [this message]
2019-05-08 12:45                       ` 積丹尼 Dan Jacobson
2019-05-08 13:22                         ` 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=8336lpi0ua.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35596-done@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=juri@linkov.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 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.