unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Corwin Brust <corwin@bru.st>
To: Stefan Kangas <stefan@marxist.se>
Cc: Harry Putnam <reader@newsguy.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Avoiding the cover page - emacs 28
Date: Sat, 18 Jan 2020 14:53:02 -0600	[thread overview]
Message-ID: <CAJf-WoQKFGmGGN1Ur62wNZiPjF=wGE4X3x3H61=SrJ9Zc5B+Ug@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmnNW+KHXFtFcwN1ib3CxtOU55fbAgEck5Nz4geS7V8bjw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3068 bytes --]

Hi again.

On Sat, Jan 18, 2020 at 10:46 AM Stefan Kangas <stefan@marxist.se> wrote:

> Stefan Monnier <monnier@iro.umontreal.ca> write:
>
> > > I'd like to avoid the cover page emacs displays when I open it.
> > >
> > > even with an argument like `~/' or `.' emacs opens with 2 screens, the
> > > bottom one showing the Coverpage and the top showing the opened
> > > argument.
> >
> > Have you tried to read that "coverpage" and click on the button for that
> > purpose there?
>
> I've added some comments regarding this in Bug#9248 which asks to not
> show the the splash by default when running "emacs <file>".  I'm in
> favour of this proposal.
>
> Please see the two e-mails starting from here:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=9248#23
>

I put this into the thread Stefan Kangas links here also, but:

I had trouble finding this button.  Looking a little bit into startup.el
suggests the button to quickly customize inhibiting splash isn't shown,
essentially, unless the slash page is being shown because the user has
explicitly invoked it sometime after startup (I think it's "after a buffer
has been opened", really).

I'm looking using GNU 26.3 on Windows 10 and started digging at
`fancy-startup-screen', called from `display-startup-screen', called from
`command-line-1', called from `command-line'.  I had a very real sense of
'there be dragons' reading startup.el but I'm *fairly* sure that the
conditional logic around whether to display a "concise" version of the
startup page is based on whether there are any buffers opened yet (display
concisely if there are), and that the button mentioned only shows in the
concise view (see line 1771 of the 26.3 release version of startup.el).

I wonder if the logic to display or not display the button is wrong, maybe
unnecessary.

Is it likely people would manually fire up the splash screen to get at this
button?  This looks like it has the same effect as customizing the specific
option and saving the customization which I'm assuming we probably learn
before figuring out how to manually launch the splash page.  I used M-:
(fancy-startup-screen) and (fancy-startup-screen t) after not finding an
interactive wrapper.  The interactive functions in (my version of)
startup.el are `display-about-screen' (not the same info and, obviously, no
buttons for directly changing startup behavior here) and
`exit-splash-screen'.

I'm tempted to submit a patch that simply inverts changes the condition to
~(null concise)~.
*But* should there also be an interactive wrapper to display the startup
screen given it maybe has special-case behaviour just for this that we've
no easy way to get at? (Not on the menu and takes a lambda or user defun to
add currently, I think)

I'm not sure if it's worth repeating my arguments here and splitting
> the discussion in two.  It might be better that those interested
> instead replies to that bug report?
>

I've responded to both places, I'm afraid.  To your point worse: this is
the better more readable version.

-- 
*Corwin*
*corwin@bru.st <corwin@bru.st>*

[-- Attachment #2: Type: text/html, Size: 4580 bytes --]

      reply	other threads:[~2020-01-18 20:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 13:28 Avoiding the cover page - emacs 28 Harry Putnam
2020-01-17 13:41 ` Corwin Brust
2020-01-17 19:20   ` Harry Putnam
2020-01-17 13:43 ` Robert Pluim
2020-01-17 23:35 ` Stefan Monnier
2020-01-18 14:46   ` Harry Putnam
2020-01-18 16:43   ` Stefan Kangas
2020-01-18 20:53     ` Corwin Brust [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='CAJf-WoQKFGmGGN1Ur62wNZiPjF=wGE4X3x3H61=SrJ9Zc5B+Ug@mail.gmail.com' \
    --to=corwin@bru.st \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=reader@newsguy.com \
    --cc=stefan@marxist.se \
    /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).