all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: not.com@gmail.com, lekktu@gmail.com, mblischke@att.net,
	11612@debbugs.gnu.org, jasonr@gnu.org
Subject: bug#11612: 24.1; Defaults create warning on startup
Date: Sat, 25 Jun 2016 17:18:53 +0300	[thread overview]
Message-ID: <83por5z702.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-8fVJ55Xj4BENwExkP5-qTDJbOr5346H6k7+gj5cgDnvg@mail.gmail.com> (message from Noam Postavsky on Sat, 25 Jun 2016 09:42:31 -0400)

> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Sat, 25 Jun 2016 09:42:31 -0400
> Cc: 11612@debbugs.gnu.org, yary <not.com@gmail.com>, 
> 	Juanma Barranquero <lekktu@gmail.com>, Michael <mblischke@att.net>, Jason Rumney <jasonr@gnu.org>
> 
> > FWIW, repeating the OP's recipe, Emacs now starts with a split-window
> > configuration, with the selected window showing the *scratch* buffer,
> > and the *Warnings* buffer displaying the above-mentioned warning.  So
> > I'm not sure the original complaint is still valid.
> 
> I think the complaint is more about the wording of the message and
> less about the buffer/window configuration. So I propose rewording it
> to
> 
>     Use of `C:\.emacs' to define `HOME' is deprecated, see (emacs)
> `Windows Home'

I don't think this is significantly more clear than the current text.
"Use of `C:\.emacs' to define `HOME'" is only understandable by people
who know how Emacs on Windows defines HOME when it is not defined in
the environment.  If we want to come up with a better text, let's make
it very clear.

How about this text instead:

  Use of `C:\.emacs' without defining `HOME' in the environment is deprecated, see `Windows Home' in the Emacs manual.





  parent reply	other threads:[~2016-06-25 14:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-02 18:58 bug#11612: 24.1; Defaults create warning on startup yary
2012-06-02 19:18 ` Eli Zaretskii
2012-06-02 19:43   ` yary
2012-06-02 19:46     ` Drew Adams
2012-06-02 19:57       ` yary
2013-04-23 14:05         ` Michael
2013-04-23 17:54           ` Eli Zaretskii
2012-06-03 19:38       ` Juanma Barranquero
2012-06-04  3:50       ` Jason Rumney
2012-06-04  4:22         ` Eli Zaretskii
2012-06-04 13:24         ` Drew Adams
2016-06-25  3:28 ` Noam Postavsky
2016-06-25  4:31   ` Drew Adams
2016-06-25  8:16   ` Eli Zaretskii
2016-06-25 13:42     ` Noam Postavsky
2016-06-25 13:51       ` yary
2016-06-25 14:18       ` Eli Zaretskii [this message]
2016-06-25 15:30         ` Noam Postavsky
2016-06-25 15:40           ` Eli Zaretskii
2016-06-27  1:01             ` Noam Postavsky
2016-06-27 11:15               ` Andy Moreton
2016-06-27 12:04                 ` Noam Postavsky

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=83por5z702.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=11612@debbugs.gnu.org \
    --cc=jasonr@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=mblischke@att.net \
    --cc=not.com@gmail.com \
    --cc=npostavs@users.sourceforge.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.