public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Keisuke Nishida <kxn30@po.cwru.edu>
To: guile-emacs@sourceware.cygnus.com
Subject: Re: scheme-describe-symbol
Date: Mon, 01 May 2000 18:16:00 -0000	[thread overview]
Message-ID: <m3wvldkazj.fsf@kei.cwru.edu> (raw)
In-Reply-To: <87n1mbvp6q.fsf@PC486.Niemitalo.LAN>

Kalle Olavi Niemitalo <tosi@ees2.oulu.fi> writes:

> >   (foo bar)
> >        ^
> > One may want to search for `foo' when one type C-h f and for `bar'
> > when one type C-h v.  So I guess we should define one function
> > `scheme-describe-object' and two commands `scheme-describe-function'
> > and `scheme-describe-variable'.  How about that?
> 
> So the functions would default to different symbols when called
> interactively, and would otherwise be identical?  Hmm... I think
> I'd prefer using the prefix argument to choose between them.

Yes, they would.  I don't think using the prefix argument is easier to
use here.  We use separate commands in Emacs Lisp, and I prefer the same
key bindings as them.  (I could customize them, though.)

> Still... currently, C-h f explains Emacs functions and C-h C-i
> explains non-Emacs symbols based on the major mode.  I think this
> is a good separation and C-h f should not be used for e.g. C
> functions.  If the only Emacs languages are Lisp and Scheme, do
> we need a language selection menu?  It would be simpler to have
> `describe-function' on C-h f and `scheme-describe' on C-h d.
> Except that doesn't solve M-:.

Probably you are right.  A variable in a language other than Lisp or
Scheme cannot have a value within Emacs, so especially describe-variable
may not be useful for those languages...  I would prefer to type C-u M-:
to choose a language (and default is decided by major-mode).

> Would each buffer using the same major mode have its own instance
> of the major-mode class?

Possibly.  We need to discuss this later on.

  reply	other threads:[~2000-05-01 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-29  1:25 scheme-describe-symbol Kalle Olavi Niemitalo
2000-04-29  2:12 ` scheme-describe-symbol Keisuke Nishida
2000-04-29 11:37   ` scheme-describe-symbol Kalle Olavi Niemitalo
2000-04-29 12:22     ` scheme-describe-symbol Keisuke Nishida
2000-04-30  6:57       ` scheme-describe-symbol Kalle Olavi Niemitalo
2000-05-01 18:16         ` Keisuke Nishida [this message]
2000-04-29 11:37   ` scheme-describe-symbol Kalle Olavi Niemitalo
2000-04-29 12:42     ` scheme-describe-symbol Keisuke Nishida

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3wvldkazj.fsf@kei.cwru.edu \
    --to=kxn30@po.cwru.edu \
    --cc=guile-emacs@sourceware.cygnus.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).