From: Thien-Thi Nguyen <ttn@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Helm (and?) or Icicles (possibly using Evil)
Date: Thu, 24 Apr 2014 19:48:30 +0200 [thread overview]
Message-ID: <87sip2y5xt.fsf@zigzag.favinet> (raw)
In-Reply-To: <0d24af8b-a235-4c4e-b946-408c74d849a0@googlegroups.com> (Hans BKK's message of "Wed, 23 Apr 2014 19:51:23 -0700 (PDT)")
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
() Hans BKK <hansbkk@gmail.com>
() Wed, 23 Apr 2014 19:51:23 -0700 (PDT)
I'm not sure what may have given the impression
I intended to do that 'shaking up the big sack thing'
Well, here is one fragment that gives that impression:
It's true I don't intend to DO, but definitely plan
to select/create STUFF that won't interfere [...]
the key word being "won't" ≡ "will not". The gist is that you choose to
partition your interaction w/ Emacs into two temporal phases. Setting
up the latter phase while still in the former is the "shaking up" part.
The "sack" part is because you represent yourself as outside, even now,
and seem to enjoy selectively-binding (yuk yuk) the membrane. The "big"
part is because Emacs is a multiverse ameoba, more oozing than snoozing.
(NB: This is not a criticism, just mawkish pining for a.r.emacs -- feel
free to ignore.)
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-04-24 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 13:20 Helm (and?) or Icicles (possibly using Evil) Hans BKK
2014-04-23 15:59 ` Drew Adams
2014-04-24 2:51 ` Hans BKK
2014-04-24 13:53 ` Drew Adams
2014-04-24 17:48 ` Thien-Thi Nguyen [this message]
[not found] ` <mailman.11.1398388920.1147.help-gnu-emacs@gnu.org>
2014-04-25 16:17 ` Emanuel Berg
2014-04-27 20:09 ` Michael Heerdegen
2014-04-28 13:45 ` Le Wang
2014-04-28 14:05 ` Michael Heerdegen
2014-04-26 21:31 ` Hans BKK
2014-04-26 22:38 ` Emanuel Berg
2014-04-26 22:58 ` Emanuel Berg
2014-04-28 11:06 ` Hans BKK
2014-04-28 13:52 ` Michael Heerdegen
2014-04-28 15:45 ` Hans BKK
2014-04-28 15:53 ` Hans BKK
2014-04-28 23:07 ` 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=87sip2y5xt.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--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).