unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, 1853@emacsbugs.donarmstrong.com,
	emacs-devel@gnu.org, handa@m17n.org
Subject: bug#1853: Trouble with gzipped info files on Windows
Date: Sun, 18 Jan 2009 16:01:40 -0500	[thread overview]
Message-ID: <jwvprik49dr.fsf-monnier+emacsbugreports__21261.8678030141$1232313959$gmane$org@gnu.org> (raw)
In-Reply-To: <ur6322f4d.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Jan 2009 16:15:14 +0200")

> Upon further thought, perhaps we want the default coding-systems to
> have an explicit -dos EOL type on DOS and Windows, for consistency
> with how we set up things on startup.  This would involve explicitly
> changing eol-type of default-coding before the last line above.

Ideally, it should not only do the same as done on startup, but also do
it by running the same code.


        Stefan






  parent reply	other threads:[~2009-01-18 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <utz7y2i31.fsf@gnu.org>
2009-01-10 21:49 ` bug#1853: Trouble with gzipped info files on Windows Juanma Barranquero
2009-01-17 13:20   ` bug#1853: marked as done (Trouble with gzipped info files on Windows) Emacs bug Tracking System
2009-01-24 15:45   ` Emacs bug Tracking System
2009-01-17 14:05 ` bug#1853: Trouble with gzipped info files on Windows Eli Zaretskii
     [not found] ` <uskni2fkf.fsf@gnu.org>
2009-01-17 14:15   ` Eli Zaretskii
     [not found]   ` <ur6322f4d.fsf@gnu.org>
2009-01-18 21:01     ` Stefan Monnier [this message]
     [not found]     ` <jwvprik49dr.fsf-monnier+emacsbugreports@gnu.org>
2009-01-19  4:11       ` Eli Zaretskii
     [not found]       ` <uwscsue81.fsf@gnu.org>
2009-01-20  5:10         ` Stefan Monnier
     [not found]         ` <jwvpriiftrm.fsf-monnier+emacsbugreports@gnu.org>
2009-01-24 15:34           ` Eli Zaretskii

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='jwvprik49dr.fsf-monnier+emacsbugreports__21261.8678030141$1232313959$gmane$org@gnu.org' \
    --to=monnier@iro.umontreal.ca \
    --cc=1853@emacsbugs.donarmstrong.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=lekktu@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).