unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Markus Grunwald <markus.grunwald@gmx.de>
To: help-gnu-emacs@gnu.org
Subject: Solved: Re: Can't find features when converting from xemacs to emacs
Date: 29 Nov 2007 13:44:46 GMT	[thread overview]
Message-ID: <474ec24e$0$27133$9b4e6d93@newsspool1.arcor-online.net> (raw)
In-Reply-To: yoijtzn5vogm.fsf@remote1.student.chalmers.se

Hello,

> (info "(emacs) Imenu")
> http://groups.google.com/group/gnu.emacs.sources/
> msg/7868f732c96484c4?output=gplain The standard Emacs branch can't do
> that,

Many thanks, now my configuration seems complete.

cu 
Markus

      reply	other threads:[~2007-11-29 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 15:58 Can't find features when converting from xemacs to emacs Markus Grunwald
2007-11-29  1:18 ` Johan Bockgård
2007-11-29 13:44   ` Markus Grunwald [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='474ec24e$0$27133$9b4e6d93@newsspool1.arcor-online.net' \
    --to=markus.grunwald@gmx.de \
    --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).