unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Menu-based tutorial?
Date: Thu, 17 May 2012 19:04:41 -0700 (PDT)	[thread overview]
Message-ID: <3a135ebd-39a6-4474-81af-64f7bb6a3eb3@e9g2000pbh.googlegroups.com> (raw)
In-Reply-To: 8d46baf5-4dcc-4bef-8245-a8534aa350c5@googlegroups.com

On May 18, 6:37 am, Karra <karra....@gmail.com> wrote:
> 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.

Any taxonomy implies an ontology -- implied, unconscious or
intentional is another matter.
And the atomic building blocks for communicating these are likely to
be completely arbitrary.
We dont ask questions like:
- What in the (shape of character) '2' suggests that it is twice of
'1'?
- What is the logical progression from 'A' to 'B' to 'C'?

These signs are less arbitrary in a pictogramic language like Chinese.
And presumably we all found these signs arbitrary at some early age
and then we 'grew up' by getting used to such arbitrariness.

Likewise the details of the contents and organization of:
File Edit View.... Help
is likely to be arbitrary, but no more arbitrary than the progression
of keys:
C-x 1, C-x 2, C-x 3, C-x 4.


      reply	other threads:[~2012-05-18  2:04 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
2012-05-18  2:04     ` rusi [this message]

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=3a135ebd-39a6-4474-81af-64f7bb6a3eb3@e9g2000pbh.googlegroups.com \
    --to=rustompmody@gmail.com \
    --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).