unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jason Rumney <jasonr@gnu.org>
Cc: cyd@stupidchicken.com, eliz@gnu.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [gmane.emacs.bugs] Emacs fails to start properly if the current working directory is on a vfat or ntfs filesystem
Date: Mon, 25 Feb 2008 20:57:47 -0500	[thread overview]
Message-ID: <jwvablojxi3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <47C35614.6020407@gnu.org> (Jason Rumney's message of "Mon, 25 Feb 2008 23:58:12 +0000")

> Here is a patch against EMACS_22_BASE.

I'd rather use a less arbitrary scheme.  E.g.
- only accept unchanged safe chars (rather than rule out
  dangerous ones), e.g. [:alnum:] and maybe a couple more.
- everything else encoded following quoted-printable.

Of course, QP applies to bytes, not to chars, which also points to
a potential problem with [:alnum:] since it includes multibyte chars
which may also be rejected, but I think that would be safe enough for
a start.

> Chong, Stefan, is it OK to check this in now, or do you want to leave
> the branch until after 22.2 is released and only fix it in the
> trunk now.

I'd include it in 22.2, tho it depends on the final shape of the code.


        Stefan




  reply	other threads:[~2008-02-26  1:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 22:00 [gmane.emacs.bugs] Emacs fails to start properly if the current working directory is on a vfat or ntfs filesystem Chong Yidong
2008-02-23 22:22 ` Eli Zaretskii
2008-02-23 22:30   ` Chong Yidong
2008-02-23 22:33   ` David Kastrup
2008-02-24  4:16     ` Eli Zaretskii
2008-02-24 14:36   ` Jason Rumney
2008-02-24 15:39     ` Stefan Monnier
2008-02-24 15:44       ` Miles Bader
2008-02-24 16:01         ` Jason Rumney
2008-02-24 19:44           ` Eli Zaretskii
2008-02-24 20:41         ` Stefan Monnier
2008-02-25 10:57           ` Richard Stallman
2008-02-25 15:57             ` Stefan Monnier
2008-02-26 12:36               ` Richard Stallman
2008-02-24 19:43       ` Eli Zaretskii
2008-02-24 23:04       ` Richard Stallman
2008-02-24 23:44         ` Jason Rumney
2008-02-25 19:01           ` Richard Stallman
2008-02-25 23:58             ` Jason Rumney
2008-02-26  1:57               ` Stefan Monnier [this message]
2008-02-26  3:41                 ` Chong Yidong
2008-02-26  4:53                   ` Stefan Monnier
2008-02-26  9:07                   ` Jason Rumney
2008-02-26  9:39                 ` Jason Rumney
2008-02-26 15:18                   ` Stefan Monnier
2008-02-24 22:30     ` Richard Stallman
2008-02-24 15:23   ` Richard Stallman
2008-02-24 20:01     ` Eli Zaretskii
2008-02-25 10:57       ` Richard Stallman
2008-02-25 20:04         ` Eli Zaretskii
2008-02-25 20:52           ` Andreas Schwab

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=jwvablojxi3.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=rms@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.
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).