From: Karra <karra.etc@gmail.com>
To: help-gnu-emacs@gnu.org
Cc: rusi <rustompmody@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: Menu-based tutorial?
Date: Thu, 17 May 2012 18:37:35 -0700 (PDT) [thread overview]
Message-ID: <8d46baf5-4dcc-4bef-8245-a8534aa350c5@googlegroups.com> (raw)
In-Reply-To: <mailman.1260.1337240896.855.help-gnu-emacs@gnu.org>
On Thursday, May 17, 2012 1:12:35 PM UTC+5:30, Thien-Thi Nguyen wrote:
> Implicit in menu presentation and interaction is a (usually)
> inscrutable ontology, which personally, i find extremely
> intimidating.
You mean an incomplete, and often poorly thought through taxonomy? Calling it an ontology is bestowing too much prestige, I'd say.
next prev parent reply other threads:[~2012-05-18 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 6:36 Menu-based tutorial? rusi
2012-05-17 7:42 ` Thien-Thi Nguyen
2012-05-17 14:08 ` Drew Adams
[not found] ` <mailman.1260.1337240896.855.help-gnu-emacs@gnu.org>
2012-05-18 1:37 ` Karra [this message]
2012-05-18 2:04 ` rusi
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=8d46baf5-4dcc-4bef-8245-a8534aa350c5@googlegroups.com \
--to=karra.etc@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rustompmody@gmail.com \
/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).