From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: viper-mode C-[ behavior change in Emacs 24.4
Date: Sun, 03 Aug 2014 02:20:22 +0200 [thread overview]
Message-ID: <87mwbmwhix.fsf@debian.uxu> (raw)
In-Reply-To: mailman.6493.1407022443.1147.help-gnu-emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Isn't it good that he asked on gnu.emacs.help so
>> that you can tell him it is a bug so that he can
>> report it?
>
> No, it's just a waste of my time.
Of course *now* the OP knows it is a bug, probably he
didn't know that when he posted, unless he (very
unlikely) was unware of the bug report function.
>> Often it is not clear if something is a bug and most
>
> If something used to work and now fails to work in
> your non-released piece of software, then you should
> always report it as a bug. Of course, we may reply
> "this is explained in the NEWS file", so double check
> the NEWS file first.
Yes, this is better - general guidelines (or
"instructions" downright) what to do - FAQ material (if
it isn't there already).
Question: "Non-released" software, I suppose that
includes the emacs24 (or 24.3+1-4+b1) or
GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.12.2)
of 2014-06-06 on barber, modified by Debian
because I have the same problem, as said. Do you have
to get it from the stable Debian repositories for it to
be "released"?
--
underground experts united
next prev parent reply other threads:[~2014-08-03 0:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6313.1406761860.1147.help-gnu-emacs@gnu.org>
2014-07-30 23:50 ` viper-mode C-[ behavior change in Emacs 24.4 Emanuel Berg
2014-07-31 14:21 ` iquiw
2014-07-31 15:33 ` Stefan Monnier
[not found] ` <mailman.6358.1406820856.1147.help-gnu-emacs@gnu.org>
2014-07-31 20:22 ` Emanuel Berg
2014-08-02 23:33 ` Stefan Monnier
[not found] ` <mailman.6493.1407022443.1147.help-gnu-emacs@gnu.org>
2014-08-03 0:20 ` Emanuel Berg [this message]
2014-08-03 2:22 ` iquiw
2014-08-04 12:53 ` Robert Thorpe
2014-08-08 14:35 ` Hans BKK
2014-08-08 17:40 ` Emanuel Berg
[not found] <mailman.6650.1407284800.1147.help-gnu-emacs@gnu.org>
2014-08-06 0:52 ` Emanuel Berg
[not found] <mailman.6544.1407156832.1147.help-gnu-emacs@gnu.org>
2014-08-05 0:03 ` Emanuel Berg
2014-08-06 0:26 ` Robert Thorpe
2014-08-07 10:40 ` Stefan Monnier
2014-08-07 15:39 ` York Zhao
[not found] ` <mailman.6775.1407426002.1147.help-gnu-emacs@gnu.org>
2014-08-08 14:14 ` iku.iwasa
[not found] ` <mailman.6746.1407408075.1147.help-gnu-emacs@gnu.org>
2014-08-07 20:58 ` Emanuel Berg
2014-08-07 21:58 ` Stefan Monnier
[not found] ` <mailman.6797.1407448766.1147.help-gnu-emacs@gnu.org>
2014-08-07 22:19 ` Emanuel Berg
2014-08-07 22:32 ` John Mastro
2014-08-07 22:54 ` Stefan Monnier
[not found] ` <mailman.6799.1407450769.1147.help-gnu-emacs@gnu.org>
2014-08-07 22:55 ` Emanuel Berg
[not found] ` <mailman.6800.1407452119.1147.help-gnu-emacs@gnu.org>
2014-08-07 23:04 ` Emanuel Berg
2014-08-08 1:33 ` Robert Thorpe
2014-07-30 14:10 iquiw
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=87mwbmwhix.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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).