unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs 21 or snapshot?
Date: Sat, 12 May 2007 21:02:48 +0200	[thread overview]
Message-ID: <85sla1c1bb.fsf@lola.goethe.zz> (raw)
In-Reply-To: slrnf4c35e.59g.wbp@L1422169.w-intra.net

wbp@nodomain.invalid (Will Parsons) writes:

> Maciej Katafiasz wrote:
>> Den Sat, 12 May 2007 08:31:25 +0200 skrev Xavier Maillard:
>> 
>>> If I was not coding modes/packages for GNU Emacs, I would have
>>> probably sticked to GNU Emacs 21.x, for sure.
>> 
>> Using Emacs 21.x now is simply silly. With 22 being almost there, it's as
>> much, or more stable than 21.x, and it has *tons* of overall improvements,
>
> So, you didn't see my response to another post in this thread, mentioning
> that I'm having problems editing remote files with the current Emacs 22 on
> Windows?

Then, for heaven's sake, file a bug report.

M-x report-emacs-bug RET

Or you will have the same problem with a _released_ version of Emacs
later.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-05-12 19:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 12:15 Emacs 21 or snapshot? Mark Woodward
2007-05-02 18:21 ` Tom Rauchenwald
2007-05-02 21:52 ` Xavier Maillard
2007-05-03  5:52 ` Kevin Rodgers
     [not found] ` <mailman.150.1178147431.32220.help-gnu-emacs@gnu.org>
2007-05-03  9:14   ` David Kastrup
2007-05-03 20:20     ` Xavier Maillard
     [not found]     ` <mailman.197.1178228441.32220.help-gnu-emacs@gnu.org>
2007-05-03 22:24       ` David Kastrup
2007-05-05 13:28         ` Xavier Maillard
     [not found]         ` <mailman.300.1178376206.32220.help-gnu-emacs@gnu.org>
2007-05-05 14:43           ` David Kastrup
2007-05-12  6:31             ` Xavier Maillard
2007-05-12 10:53               ` Maciej Katafiasz
     [not found]               ` <mailman.556.1178967706.32220.help-gnu-emacs@gnu.org>
2007-05-12 18:51                 ` Will Parsons
2007-05-12 19:02                   ` David Kastrup [this message]
2007-05-15 18:26                     ` Will Parsons
2007-05-15 18:46                       ` Peter Dyballa
2007-05-15 18:46                       ` Lennart Borgman (gmail)
2007-05-13  3:25                   ` Giorgos Keramidas
2007-05-15 18:33                     ` Will Parsons
2007-05-15 23:39                       ` Giorgos Keramidas
     [not found]             ` <mailman.547.1178957352.32220.help-gnu-emacs@gnu.org>
2007-05-12  9:55               ` David Kastrup
     [not found]         ` <slrnf3sjbc.4ki.oudeis@isis.thalatta.eme>
2007-05-07 17:49           ` Lennart Borgman (gmail)
     [not found]           ` <mailman.374.1178560583.32220.help-gnu-emacs@gnu.org>
2007-05-10 17:09             ` Will Parsons
2007-05-11  4:56               ` Stefan Monnier
2007-05-11 17:16                 ` Will Parsons
2007-05-11  4:57               ` Stefan Monnier
2007-05-11 17:24                 ` Will Parsons
2007-05-04 12:37       ` Hadron
2007-05-04 15:01         ` Sebastian Tennant
     [not found]         ` <mailman.229.1178291246.32220.help-gnu-emacs@gnu.org>
2007-05-05  1:10           ` David Kastrup
2007-05-05 13:30         ` Xavier Maillard
2007-05-03 10:18   ` Hadron
2007-05-05  1:01 ` Mark Woodward

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=85sla1c1bb.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --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).