unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>,
	Michael Heerdegen <michael_heerdegen@web.de>,
	help-gnu-emacs@gnu.org
Subject: RE: Easy/Possible to globally change prompt strings of messages? e.g. changing find-file's prompt string from "Find file:" to "open file:" ?
Date: Mon, 2 Feb 2015 14:11:31 -0800 (PST)	[thread overview]
Message-ID: <2aa3a8e0-b8a0-40cd-bd9b-550dffa921ec@default> (raw)
In-Reply-To: <87egq8ugz6.fsf@wmi.amu.edu.pl>

> > OK.  Thanks everyone for your help.  I think I'll just get used to "Find
> > file" for now. :)
> 
> For now.  Yeah, sure.
> And in five years, when some Emacs newbie asks you about all those
> strange terms, you'll say: "Young \(wo\)?man, forget about the newspeak
> of opening files in panes, using tabs, cutting and pasting, moving the
> cursor and pressing Ctrl+F.  Instead, embrace the ancient wisdom of
> visiting files in windows, using buffers, killing and yanking, moving
> the point and pressing C-s."  Welcome to the rabbit hole.

Yup.  "Ancient wisdom" or not, rabbit hole or not, that's the Emacs
jargon.

Suppose you do change things locally to teach Emacs not to use its
own jargon etc. - and you can do so to different degrees, though it
might mean jumping through a few hoops (is it worth it?).

Then you have difficulty communicating with (e.g., helping) others,
because that jargon is what is used by the application itself and its
community.

For better or worse.  Learn to speak Emacs - that's my advice.  Whether
you think it represents "ancient wisdom" or not.  And if you feel strongly
about some bit of jargon, then argue on emacs-devel@gnu.org to change it.



  reply	other threads:[~2015-02-02 22:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30  4:08 Easy/Possible to globally change prompt strings of messages? e.g. changing find-file's prompt string from "Find file:" to "open file:" ? Chris Seberino
2015-01-30  4:19 ` Drew Adams
2015-01-30  5:03   ` Christian Seberino
2015-01-30  8:42     ` Michael Heerdegen
2015-01-30 16:19       ` [OT] " Harry Putnam
2015-01-30 16:33         ` Drew Adams
2015-02-05 20:57           ` Harry Putnam
2015-02-05 21:41             ` Michael Heerdegen
2015-02-06 14:35               ` Harry Putnam
2015-01-30 14:41     ` Drew Adams
2015-01-30 23:30       ` Christian Seberino
2015-01-31  0:31         ` Drew Adams
2015-01-31  0:35           ` Christian Seberino
2015-01-31  0:38             ` Christian Seberino
2015-02-01 13:55               ` Michael Heerdegen
2015-02-01 23:18                 ` Christian Seberino
2015-02-02 21:43                   ` Marcin Borkowski
2015-02-02 22:11                     ` Drew Adams [this message]
     [not found]                     ` <mailman.19192.1422915104.1147.help-gnu-emacs@gnu.org>
2015-02-03  3:31                       ` Rusi
     [not found]     ` <mailman.18960.1422607363.1147.help-gnu-emacs@gnu.org>
2015-01-30 23:58       ` Chris Seberino
2015-02-01 13:51         ` Michael Heerdegen

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=2aa3a8e0-b8a0-40cd-bd9b-550dffa921ec@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mbork@wmi.amu.edu.pl \
    --cc=michael_heerdegen@web.de \
    /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).