Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Felix Natter <fnatter@gmx.net>
Cc: info-gnus-english@gnu.org
Subject: Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")
Date: Tue, 02 Apr 2013 10:40:59 +0900	[thread overview]
Message-ID: <b4mvc85yaj8.fsf@jpl.org> (raw)
In-Reply-To: <mailman.23213.1364818828.855.info-gnus-english@gnu.org>

Felix Natter <fnatter@gmx.net> wrote:
> Will Ma Gnus also work with GNU Emacs 23?

It should work.  I tried to build Emacs 23.4 but failed (this
seems to need some tweaks to build on Cygwin).  But don't worry,
in the past I had a chance to use the Emacs 23.4 binary that
Cygwin distributed and the one I built on Linux in home, and had
no problem with Ma Ggnus.  AFAICT, the significant difference
between the old Gnus and today's one is that the marks feature
for the nnml backend, etc. has been removed.  But it won't trouble
you unless you run two or more Gnus on the same account of the
same machine.

[...]

>> You can simply abandon Ma Gnus by:
>> ・ rm -r site-lisp/gnus
>> ・ remove the (require 'gnus-load) line in the ~/.emacs file.

> But Ma Gnus won't change the configuration so that the "stable" Gnus
> that comes with Emacs(23) does not run any more? In other words, can I
> always go back?

I believe you can go back with no major problem.  If anything, I
don't think you get a reason to go back.  Even if it causes a
trouble, you will be able to get more followups in the net since
the interest of developers and expert users is in the bleeding
edge, not the old ones.  What you have to do then is to download
and rebuild the improved Gnus, or to improve it by yourself.

  parent reply	other threads:[~2013-04-02  1:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.19525.1360518618.855.info-gnus-english@gnu.org>
2013-02-13  0:18 ` Katsumi Yamaoka
2013-03-25 20:41   ` Felix Natter
     [not found]   ` <mailman.22829.1364244138.855.info-gnus-english@gnu.org>
2013-03-26  1:50     ` Katsumi Yamaoka
2013-03-26 19:58       ` Felix Natter
     [not found]       ` <mailman.22889.1364327929.855.info-gnus-english@gnu.org>
2013-03-27  0:17         ` Katsumi Yamaoka
2013-03-27 18:29           ` Felix Natter
     [not found]           ` <mailman.22943.1364408991.855.info-gnus-english@gnu.org>
2013-03-28  1:36             ` Expiring sent drafts does now always `delete' Katsumi Yamaoka
2013-03-31 18:19           ` Sent message still in drafts (lisp error: "Selecting deleted buffer") Felix Natter
2013-03-31 23:48             ` Katsumi Yamaoka
2013-03-31 23:59               ` Katsumi Yamaoka
2013-04-01  7:31                 ` Felix Natter
     [not found]                 ` <mailman.23203.1364801493.855.info-gnus-english@gnu.org>
2013-04-01  9:44                   ` Katsumi Yamaoka
2013-04-01 12:20                     ` Felix Natter
     [not found]                     ` <mailman.23213.1364818828.855.info-gnus-english@gnu.org>
2013-04-02  1:40                       ` Katsumi Yamaoka [this message]
2013-02-10 17:49 Felix Natter

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=b4mvc85yaj8.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=fnatter@gmx.net \
    --cc=info-gnus-english@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 NNTP newsgroup(s).