unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Uday Reddy <usr.vm.rocks@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: kzhr@d1.dion.ne.jp, monnier@IRO.UMontreal.CA,
	Uday Reddy <usr.vm.rocks@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Emacs24 coding system problems
Date: Sun, 25 Nov 2012 23:37:14 +0000	[thread overview]
Message-ID: <20658.43946.898000.250218@gargle.gargle.HOWL> (raw)
In-Reply-To: <831ufhz8pl.fsf@gnu.org>

Eli Zaretskii writes:

> > Date: Sun, 25 Nov 2012 19:58:25 +0000
> > From: Uday Reddy <usr.vm.rocks@gmail.com>
> > Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>,
> > 	Uday Reddy <usr.vm.rocks@gmail.com>, emacs-devel@gnu.org
> > 
> > I am surprised that Emacs24 shipped with such a glaring bug.
> 
> No one uses that variable anymore.  Since it was removed (Feb 2011!)
> no one complained until now.  So I think "glaring bug" is a glaring
> exaggeration.

Hmm.  Eli, it looks like you haven't read Kazuhiro's bug report closely.
find-file-noselect is setting the variable.  We are not.

Cheers,
Uday





  reply	other threads:[~2012-11-25 23:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02  8:24 Emacs24 coding system problems Uday Reddy
2012-11-02  8:39 ` Andreas Schwab
2012-11-02  8:51   ` Eli Zaretskii
2012-11-02  8:56     ` Eli Zaretskii
2012-11-18 19:06     ` Uday Reddy
2012-11-18 21:07       ` Eli Zaretskii
2012-11-19  4:05         ` Stephen J. Turnbull
2012-11-19  8:43         ` Uday Reddy
2012-11-24 20:29           ` Stefan Monnier
2012-11-25  7:58             ` Uday Reddy
2012-11-25 10:44               ` Uday Reddy
2012-11-25 16:06                 ` Eli Zaretskii
2012-11-25 20:36                   ` Uday Reddy
2012-11-25 21:10                     ` Eli Zaretskii
2012-11-25 11:48               ` Kazuhiro Ito
2012-11-25 19:58                 ` Uday Reddy
2012-11-25 21:14                   ` Eli Zaretskii
2012-11-25 23:37                     ` Uday Reddy [this message]
2012-11-26  3:41                       ` Eli Zaretskii
2012-11-26  8:30                         ` Kazuhiro Ito
2012-11-26 17:16                           ` Eli Zaretskii
2012-11-28 12:39                             ` Kazuhiro Ito
2012-11-28 17:40                               ` Eli Zaretskii
2012-11-28 21:16                             ` Uday S Reddy
2012-11-29  3:46                               ` Eli Zaretskii
2012-11-30 10:58                                 ` Uday Reddy
2012-11-30 13:40                                   ` Eli Zaretskii
2012-12-02  0:46                                     ` Emacs24 unpredictable behaviour [Was: coding system problems] Uday Reddy
2012-12-02  8:06                                       ` Andreas Schwab
2012-12-02 11:42                                       ` Uday Reddy
2012-11-09 17:01 ` Emacs24 coding system problems Stefan Monnier

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=20658.43946.898000.250218@gargle.gargle.HOWL \
    --to=usr.vm.rocks@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kzhr@d1.dion.ne.jp \
    --cc=monnier@IRO.UMontreal.CA \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).