From: Yuri Khan <yuri.v.khan@gmail.com>
To: Emanuel Berg <embe8573@student.uu.se>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: shell-CLI for Emacs
Date: Mon, 26 Aug 2013 11:03:39 +0700 [thread overview]
Message-ID: <CAP_d_8Wuf+N2n+=VBrm7G5O1AOO-WvuLEQr7R8xu_GQTjvGtrg@mail.gmail.com> (raw)
In-Reply-To: <8738px9smb.fsf@nl106-137-194.student.uu.se>
On Mon, Aug 26, 2013 at 7:56 AM, Emanuel Berg <embe8573@student.uu.se> wrote:
>> That's the primary benefit of all DWIM hacking, after all, for
>> both you and Emacs!
>
> DWIM, is that what I'm doing? Why did you say that? I'm to read
> the Wikipedia article tonight - never heard of it, but intuitively
> I like it.
>
> add_dic () { sudo tar -xvjf $1 -C /usr/share/stardict/dic; }
What you are doing here is just programming: replacing a long precise
command with a shorter but still precise command.
DWIM is a technique of replacing a precise command with one that is in
some way imprecise. You misspell a command, something behind the
scenes corrects it for you (seen in zsh). You don’t specify a
parameter, it picks a default that is sensible for some people in some
cases, but not universally (e.g. git push).
You should be reading not Wikipedia but The Jargon File:
http://www.catb.org/~esr/jargon/html/D/DWIM.html . It explains well
why one man’s Do What I Mean is another’s Damn Warren’s Infernal
Machine.
next prev parent reply other threads:[~2013-08-26 4:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.664.1377295372.10748.help-gnu-emacs@gnu.org>
2013-08-23 22:42 ` shell-CLI for Emacs Emanuel Berg
2013-08-24 0:37 ` Thien-Thi Nguyen
[not found] ` <mailman.670.1377304488.10748.help-gnu-emacs@gnu.org>
2013-08-24 3:30 ` Emanuel Berg
2013-08-26 0:56 ` Emanuel Berg
2013-08-26 4:03 ` Yuri Khan [this message]
2013-08-26 5:38 ` Thien-Thi Nguyen
2013-08-23 22:02 Barry OReilly
-- strict thread matches above, loose matches on Subject: below --
2013-08-23 20:46 Emanuel Berg
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='CAP_d_8Wuf+N2n+=VBrm7G5O1AOO-WvuLEQr7R8xu_GQTjvGtrg@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=embe8573@student.uu.se \
--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).