unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Juri Linkov <juri@jurta.org>
Subject: prexix argument of Info-copy-current-node-name
Date: Wed, 25 Oct 2006 18:06:41 +0200	[thread overview]
Message-ID: <v964e8xtv2.fsf@marauder.physik.uni-ulm.de> (raw)

Hi,

`Info-copy-current-node-name' requires a _zero_ prefix argument to
copy the strings like ``(info "(emacs)Top")'' into the kill ring:

,----[ <f1> f Info-copy-current-node-name RET ]
| Info-copy-current-node-name is an interactive compiled Lisp function
| in `info'.  (Info-copy-current-node-name &optional ARG)
| 
| Put the name of the current Info node into the kill ring.
| The name of the Info file is prepended to the node name in parentheses.
| With a zero prefix arg, put the name inside a function call to `info'.
`----

>From Juri's suggestion on emacs-devel [1] I understand that `M-0 w'
(or `C-u 0 w') was because of the analogy to
`dired-copy-filename-as-kill' [2].  But wouldn't it make more sense to
allow _any_ prefix argument in `Info-copy-current-node-name'?

Bye, Reiner.

[1] http://thread.gmane.org/gmane.emacs.devel/23888/

[2]
,----[ <f1> f dired-copy-filename-as-kill RET ]
| dired-copy-filename-as-kill is an interactive compiled Lisp function
| in `dired'.  (dired-copy-filename-as-kill &optional ARG)
| 
| Copy names of marked (or next ARG) files into the kill ring.
| The names are separated by a space.
| With a zero prefix arg, use the absolute file name of each marked file.
| With C-u, use the file name relative to the dired buffer's
| `default-directory'.  [...]
`----
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

             reply	other threads:[~2006-10-25 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 16:06 Reiner Steib [this message]
2006-10-25 20:43 ` prexix argument of Info-copy-current-node-name Juri Linkov
2006-10-30 15:13   ` Reiner Steib
2006-10-31  0:18     ` Richard Stallman

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=v964e8xtv2.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=juri@jurta.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).