unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <1187@emacsbugs.donarmstrong.com>
Subject: bug#1187: closed by Stefan Monnier <monnier@iro.umontreal.ca> (Re: bug#1187: 23.0.60; Cannot read vline.el - invalid read syntax)
Date: Fri, 17 Oct 2008 09:48:08 -0700	[thread overview]
Message-ID: <002601c93078$222fb350$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <handler.1187.D1187.122425837312105.notifdone@emacsbugs.donarmstrong.com>

> This is an automatic notification regarding your bug report
> which was filed against the emacs package:
> 
> #1187: 23.0.60; Cannot read vline.el - invalid read syntax
> 
> It has been closed by Stefan Monnier <monnier@iro.umontreal.ca>.
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Stefan 
> Monnier <monnier@iro.umontreal.ca> by replying to this email.

[Note: "replying to this email" - even Reply All, does *not* send anything to
monnier@iro.umontreal.ca. That address needs to be added by hand, apparently.]


Uh, why was this closed in the middle of debugging and a discussion about it?

 http://www.emacswiki.org/cgi-bin/emacs/download/vline.el contains
 non-ascii chars, but does not contain any coding tag, so depending on
 your coding settings, it will decode it in different ways, some of which
 will lead to load-time errors, others to incorrect behavior.
 There's nothing for Emacs to do here.
 Such uses are OK for a file you wrote for your own use, but for
 distribution to people who may use other locales, it's not.

Not too helpful. Please explain what the author needs to do to fix the file.

And does the Emacs doc perhaps need to be updated to explain that libraries that
worked in Emacs 22 might need to be modified by adding coding settings in order
to work in Emacs 23?

BTW, the URL you cite does not correspond to the file I sent, as someone pointed
out, even though the file names are the same. The problem might be the same for
both files (dunno), but the reference is incorrect. This bug report you closed
is not about the file you closed it for.







      parent reply	other threads:[~2008-10-17 16:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jwv3aivjkhw.fsf-monnier+emacsbugreports@gnu.org>
2008-10-16 21:22 ` bug#1187: 23.0.60; Cannot read vline.el - invalid read syntax Drew Adams
2008-10-16 23:41   ` Lennart Borgman (gmail)
2008-10-17  0:00     ` Drew Adams
2008-10-17  8:18       ` Eli Zaretskii
2008-10-17  8:36         ` Lennart Borgman (gmail)
2008-10-17  9:57           ` Eli Zaretskii
2008-10-17  8:15   ` Eli Zaretskii
2008-10-17 14:26     ` Drew Adams
2008-10-17 12:30   ` Lawrence Mitchell
2008-10-17 13:07     ` Eli Zaretskii
2008-10-17 14:40       ` Drew Adams
2008-10-17 15:53         ` Drew Adams
2008-10-17 16:04           ` Eli Zaretskii
2008-10-17 14:58       ` Lennart Borgman (gmail)
2008-10-17 15:18         ` Drew Adams
2008-10-17 15:58           ` Lawrence Mitchell
2008-10-17 16:09             ` Drew Adams
2008-10-17 16:00           ` Eli Zaretskii
2008-10-17 16:21             ` Drew Adams
2008-10-17 18:24               ` Eli Zaretskii
2008-10-20 10:28                 ` Kenichi Handa
2008-10-20 10:58                   ` Eli Zaretskii
2008-10-21  2:40                     ` Kenichi Handa
2008-10-21  4:46                       ` Drew Adams
2008-10-17 15:55   ` bug#1187: marked as done (23.0.60; Cannot read vline.el - invalid read syntax) Emacs bug Tracking System
     [not found]   ` <handler.1187.D1187.122425837312105.notifdone@emacsbugs.donarmstrong.com>
2008-10-17 16:48     ` Drew Adams [this message]

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='002601c93078$222fb350$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=1187@emacsbugs.donarmstrong.com \
    /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).