unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Grégoire Neuville" <gregoire.neuville@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: emacs23 and ecb-2.32
Date: Fri, 28 Nov 2008 23:46:42 +0100	[thread overview]
Message-ID: <80259df90811281446o1ca03c2do130eac29aea5773d@mail.gmail.com> (raw)

Hi,

There seems to be a problem with loading ecb version 2.32 in emacs23
(actually emacs-snapshot pulled from the http://emacs.orebokech.com
debian repository).

As a matter of fact with this configuration, as soon as a special
buffer is loaded (e.g ecb configuration buffers or eshell), this
buffer is associated with the previous buffer name (thus, if I load
eshell with ecb activated and *scratch* as my current buffer, the
buffer named "eshell" is void, and the one named "*scratch*" contains
the eshell).

This behavior doesn't occur neither with emacs21 nor emacs22 on my
debian etch amd64 distribution.

Any idea ?

Thanks,
-- 
Grégoire Neuville

                 reply	other threads:[~2008-11-28 22:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=80259df90811281446o1ca03c2do130eac29aea5773d@mail.gmail.com \
    --to=gregoire.neuville@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).