From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: changes on “info” function in emacs 23
Date: Fri, 7 Aug 2009 16:31:22 -0700 (PDT) [thread overview]
Message-ID: <85fc0b81-d7cc-4a6d-94d2-a5a2b76ae6d1@x6g2000prc.googlegroups.com> (raw)
In-Reply-To: f41a99b0-d338-46e4-89e7-5bbe3ab3920a@h31g2000yqd.googlegroups.com
On Aug 4, 6:39 pm, "A.Politz" <poli...@googlemail.com> wrote:
> On Aug 5, 1:26 am, Xah Lee <xah...@gmail.com> wrote:
>
> > It still works with or without the space, but would like to read about
> > this change.
>
> > thanks.
>
> > Xah
>
> * Added one space to the output of some info function, thought it
> might look better.
>
> Now you've done it, feel free to merge this line with your NEWS file.
> BTW
> C-0 c
> , even more news.
>
> -ap
the change actually broke one of my elisp function. I have a command
that when invoked, will turn the current line like
(emacs)dired
into
<span class="ref">(info "(emacs)dired")</span>
now it broke! lol. (yeah it can be fixed in few secs)
But anyway, i did some testing, at least this extra space change is
backward compatible. e.g.
(info "(emacs)dired")
(info "(emacs) dired")
both works in emacs 22.
However, i noticed another, more important issue. In emacs 22, there's
this node:
(info "(emacs)Transient Mark")
but doesn't exit in emacs 23's manual.
Shouldn't the manual nodes be persistant across versions, e.g.
providing redirect when node changed?
as a pratical matter, this means now i have to search all my tutorial
that points to manual nodes and check if they still work. This applies
to any publication on emacs that reference to the manual by node.
this is a problem with python manual too... thinking about this,
actually i don't know if there are any manual that:
(1) provide a computable reference to the chapter/sections.
(2) maintain this on different versions of the manual.
However, since emacs does (1) already, it's easy to do (2) too.
Xah
∑ http://xahlee.org/
☄
next prev parent reply other threads:[~2009-08-07 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 23:26 changes on “info” function in emacs 23 Xah Lee
2009-08-05 1:39 ` A.Politz
2009-08-07 23:31 ` Xah Lee [this message]
2009-08-08 23:47 ` Xah Lee
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=85fc0b81-d7cc-4a6d-94d2-a5a2b76ae6d1@x6g2000prc.googlegroups.com \
--to=xahlee@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).