unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "d.henman" <dhenman@gmail.com>
To: <emacs-devel@gnu.org>
Subject: Re: Emacs-devel Digest, Vol 43, Issue 234
Date: Thu, 20 Sep 2007 16:13:45 +0900	[thread overview]
Message-ID: <20070920161345.1192@blackhawk> (raw)
In-Reply-To: Your message of Wed, 19 Sep 2007 21:16:19 -0400 <46f1ca06.0313360a.5a40.ffffa64eSMTPIN_ADDED@mx.google.com>


Yes, unwanted advertisement pop-ups, aka, splash screens are annoyances to all and
should be overriden by command line invocations at the very, very least.

Why try to emulate Microsoft, et al.

The following invocation has been and should always be the norm.

 $ emacs  filetoedit.txt

when you want to edit a file and don't want splash screens advertising whatever.

if no agrument then... you have options.....  but, always leave the option for users to defenestrate it from the X-window frame.

Darel Henman



emacs-devel-request@gnu.org wrote:
> Date: Thu, 20 Sep 2007 01:24:49 +0100
> From: Leo <sdl.web@gmail.com>
> Subject: Re: New start up splash screen annoyance...
> To: emacs-devel@gnu.org
> Message-ID: <m2wsumuqsu.fsf@cam.ac.uk>
> Content-Type: text/plain; charset=us-ascii
> 
> On 2007-09-20 00:46 +0100, Juri Linkov wrote:
> >> My mind is made up that we must arrange that beginners who always
> >> specify a file name argument mostly do see the splash screen
> >> information.  I'm willing to consider other ways of doing that
> >> as long as I think they are effective.
> >
> > The least obtrusive way to show the important information for beginners is
> > using the echo area message.  It is quite reliable channel if we take
> > precautions against overriding it with other messages (e.g. displaying it
> > at the final stage of startup).  A large message, as Kim suggested,
> > can't go unnoticed.  And clicking on it would display the full startup
> > screen.
> 
> Back in the days when I was using proprietary software, I usually needed
> to purchase a license to stop it from popping up a startup screen. It
> would be helpful if we can do the same.
> 
> -- 
> .:  Leo  :.  [ sdl.web AT gmail.com ]  .:  [ GPG Key: 9283AA3F ]  :.

           reply	other threads:[~2007-09-20  7:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <46f1ca06.0313360a.5a40.ffffa64eSMTPIN_ADDED@mx.google.com>]

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=20070920161345.1192@blackhawk \
    --to=dhenman@gmail.com \
    --cc=emacs-devel@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).