From: "Ludwig, Mark" <ludwig.mark@siemens.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: Emacs: Problems of the Scratch Buffer
Date: Thu, 19 Apr 2012 22:41:32 +0000 [thread overview]
Message-ID: <BC5672F8AD4C054BAF167C9801500D1A78D4AB46@USSLMMBX003.net.plm.eds.com> (raw)
In-Reply-To: <cc%jr.8078$8_6.426@newsfe09.iad>
> From: Chiron
> Sent: Thursday, April 19, 2012 4:12 PM
> To: help-gnu-emacs@gnu.org
> Subject: Re: Emacs: Problems of the Scratch Buffer
>
> On Thu, 19 Apr 2012 13:47:40 -0700, Bug Dout wrote:
>
> > Several good points. But given the ultra-conservative nature of
> > emacsians, changes will never be implemented. Gnu Emacs remains firmly
> > in the last century.
>
> And really, "better" is a judgement made by each user....
>
> If Emacs works for you, use it. If not, don't, or fix what you feel is
> wrong with it. It's nothing but the most highly customizable editor on
> the planet.
Right, and I appreciate learning some simple ways to make *scratch* more useful, as well as finding the stray code in .emacs that was suppressing the startup screen.
The original post was from someone who doesn't like *scratch* to be the first thing he sees. It seems clear that something in his customization is suppressing the normal startup screen (including possibly something at the site done by someone who likes seeing *scratch*...).
Cheers,
Mark
next prev parent reply other threads:[~2012-04-19 22:41 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 12:00 Emacs: Problems of the Scratch Buffer Xah Lee
2012-04-18 12:31 ` Joe Corneli
2012-04-18 16:57 ` Steinar Bang
2012-04-18 17:33 ` Ludwig, Mark
2012-04-18 18:15 ` Juanma Barranquero
2012-04-18 18:16 ` Juanma Barranquero
2012-04-19 21:08 ` Steinar Bang
[not found] ` <mailman.169.1334770417.751.help-gnu-emacs@gnu.org>
2012-04-18 21:11 ` Chiron
2012-04-18 23:56 ` Ludwig, Mark
2012-04-19 10:34 ` Tassilo Horn
2012-04-18 17:01 ` Mark Skilbeck
2012-04-18 19:33 ` Aaron Meurer
2012-04-18 20:22 ` Deniz Dogan
2012-04-19 5:55 ` Kevin Rodgers
2012-04-19 5:58 ` Kevin Rodgers
2012-04-19 20:47 ` Bug Dout
2012-04-19 21:11 ` Chiron
2012-04-19 22:41 ` Ludwig, Mark [this message]
[not found] ` <mailman.260.1334875302.751.help-gnu-emacs@gnu.org>
2012-04-20 3:27 ` Pascal J. Bourguignon
2012-04-20 3:53 ` Aaron Meurer
2012-04-20 11:08 ` Fritz Wuehler
2012-04-20 11:48 ` Richard Riley
[not found] ` <mailman.304.1334922534.751.help-gnu-emacs@gnu.org>
2012-04-21 3:53 ` Chiron
2012-04-21 8:16 ` Joost Kremers
2012-04-21 12:43 ` Chiron
2012-04-21 12:47 ` Jambunathan K
2012-04-21 14:10 ` Eli Zaretskii
[not found] ` <mailman.373.1335012467.751.help-gnu-emacs@gnu.org>
2012-04-21 14:42 ` Chiron
2012-04-21 14:49 ` Joe Corneli
[not found] ` <mailman.381.1335019797.751.help-gnu-emacs@gnu.org>
2012-04-21 15:04 ` Chiron
[not found] ` <mailman.379.1335017454.751.help-gnu-emacs@gnu.org>
2012-04-21 14:46 ` Chiron
2012-04-21 15:34 ` Eli Zaretskii
2012-04-21 16:15 ` Dan Espen
2012-04-21 16:58 ` Chiron
[not found] ` <mailman.389.1335022448.751.help-gnu-emacs@gnu.org>
2012-04-21 16:32 ` Chiron
2012-04-21 16:52 ` Eli Zaretskii
[not found] ` <mailman.396.1335027140.751.help-gnu-emacs@gnu.org>
2012-04-21 17:09 ` Chiron
2012-04-21 17:36 ` Dan Espen
2012-04-21 23:01 ` Bastien
2012-04-23 11:52 ` Joost Kremers
2012-04-24 7:40 ` rusi
2012-04-24 11:35 ` Richard Riley
2012-04-24 13:44 ` ken
2012-04-25 10:39 ` Thien-Thi Nguyen
2012-04-25 12:41 ` ken
2012-04-25 21:51 ` Jambunathan K
[not found] ` <mailman.42.1335390728.855.help-gnu-emacs@gnu.org>
2012-04-26 17:25 ` rusi
2012-04-26 17:48 ` Bastien
[not found] ` <mailman.619.1335350542.751.help-gnu-emacs@gnu.org>
2012-04-26 19:08 ` Xah Lee
2012-04-24 14:33 ` Dan Espen
2012-04-24 18:40 ` PJ Weisberg
2012-04-21 8:36 ` Thien-Thi Nguyen
2012-04-21 9:48 ` Joe Corneli
[not found] ` <mailman.362.1334997514.751.help-gnu-emacs@gnu.org>
2012-04-21 12:35 ` Chiron
2012-04-21 13:31 ` Pascal J. Bourguignon
2012-04-21 15:01 ` Chiron
2012-04-21 14:07 ` Eli Zaretskii
[not found] ` <mailman.378.1335017298.751.help-gnu-emacs@gnu.org>
2012-04-21 14:52 ` Pascal J. Bourguignon
2012-04-21 15:15 ` Jambunathan K
2012-04-21 16:03 ` Jambunathan K
2012-04-21 14:59 ` Chiron
2012-04-21 15:35 ` Eli Zaretskii
[not found] ` <mailman.390.1335022565.751.help-gnu-emacs@gnu.org>
2012-04-21 16:47 ` Chiron
2012-04-21 17:07 ` Thien-Thi Nguyen
[not found] ` <mailman.398.1335028190.751.help-gnu-emacs@gnu.org>
2012-04-21 17:14 ` Chiron
2012-04-21 17:47 ` Juanma Barranquero
[not found] ` <mailman.401.1335030473.751.help-gnu-emacs@gnu.org>
2012-04-21 18:03 ` Chiron
2012-04-21 21:34 ` Jason Earl
2012-04-21 14:39 ` Stefan Monnier
2012-04-21 15:03 ` Chiron
2012-04-20 11:31 ` Martin
2012-04-21 3:14 ` Stefan Monnier
2012-04-21 3:25 ` Dan Espen
2012-04-21 14:38 ` Stefan Monnier
2012-04-21 16:08 ` Dan Espen
2012-04-21 16:50 ` Chiron
2012-04-21 17:30 ` Dan Espen
2012-04-21 22:13 ` Ludwig, Mark
2012-04-22 10:00 ` Petter Gustad
2012-04-22 10:27 ` Richard Riley
2012-06-12 19:25 ` Nikolai Alekseev
2012-06-12 19:24 ` Nikolai Alekseev
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=BC5672F8AD4C054BAF167C9801500D1A78D4AB46@USSLMMBX003.net.plm.eds.com \
--to=ludwig.mark@siemens.com \
--cc=help-gnu-emacs@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.
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).