unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: 1187@emacsbugs.donarmstrong.com
Subject: bug#1187: 23.0.60; Cannot read vline.el - invalid read syntax
Date: Fri, 17 Oct 2008 11:57:05 +0200	[thread overview]
Message-ID: <uljwnmtn2.fsf@gnu.org> (raw)
In-Reply-To: <48F84E9F.8070702@gmail.com>

> Date: Fri, 17 Oct 2008 10:36:47 +0200
> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
> CC: Drew Adams <drew.adams@oracle.com>, 1187@emacsbugs.donarmstrong.com
> 
> Eli Zaretskii wrote:
> >> From: "Drew Adams" <drew.adams@oracle.com>
> >> Date: Thu, 16 Oct 2008 17:00:40 -0700
> >> Cc: 
> >>
> >>> Just for info: I had some similar problems and decided to set
> >>>  current-language-environment to "UTF-8"
> >> OK, thanks for the workaround.
> >>
> >> But that should not be necessary. In Emacs 22, it just DTRT. Users should be
> >> able to load the file in both Emacs versions without fiddling with the language
> >> environment.
> > 
> > But that could be a problem with vline.el itself, you know.  It uses
> > non-ASCII characters, but does not include any "coding:" cookies, so
> > Emacs is left with its guesswork for how to interpret the 8-bit bytes
> > included in the file.  And that guesswork is not fool-proof.
> > 
> > I will look at this closer after you report the details about the
> > bytes that I requested in my other message.
> 
> I do not remember; could the defaults be changed so that reading files
> like vline.el will succeed?

Obviously, that depends on the nature of the problem, which at least
to me is not yet clear.






  reply	other threads:[~2008-10-17  9:57 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 [this message]
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     ` bug#1187: closed by Stefan Monnier <monnier@iro.umontreal.ca> (Re: bug#1187: 23.0.60; " Drew Adams

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=uljwnmtn2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=1187@emacsbugs.donarmstrong.com \
    --cc=lennart.borgman@gmail.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).