unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Juanma Barranquero <lekktu@gmail.com>, emacs-devel@gnu.org
Subject: Re: Problems with the url package on w32?
Date: Fri, 22 Dec 2006 16:48:51 -0500	[thread overview]
Message-ID: <jwvtzznbo0u.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <458B1514.4070902@student.lu.se> (Lennart Borgman's message of "Fri\, 22 Dec 2006 00\:13\:24 +0100")

>> I.e. C-c C-a fails to apply the hunk (i.e. doesn't change the buffer at
>> all), and correctly tells the user about this failure?
>> If so, it's a "minor" bug.
> I think that on w32 several things can happen. The main problem is the line
> endings and the ability of different patch.exe on w32 to handle them. I sent

diff-mode's C-c C-a does not use any external tool, only elisp code.


        Stefan

  reply	other threads:[~2006-12-22 21:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ur6vodg5m.fsf@gmail.com>
     [not found] ` <871wnnclkz.fsf@freemail.hu>
     [not found]   ` <uac2acxu0.fsf@gmail.com>
     [not found]     ` <87lkltztzy.fsf@freemail.hu>
2006-12-02 11:37       ` Problems with the url package on w32? Magnus Henoch
2006-12-03  3:15         ` Richard Stallman
2006-12-03 18:25           ` Magnus Henoch
2006-12-03 21:17             ` Kim F. Storm
2006-12-19 15:48               ` Kim F. Storm
2006-12-19 23:13                 ` Juanma Barranquero
2006-12-20 11:05                   ` Kim F. Storm
2006-12-20 12:05                     ` Juanma Barranquero
2006-12-19 23:45                 ` Lennart Borgman
2006-12-19 23:54                   ` Juanma Barranquero
2006-12-20  0:04                     ` Lennart Borgman
2006-12-20  0:08                       ` Juanma Barranquero
2006-12-20  6:57                     ` Eli Zaretskii
2006-12-20  9:07                       ` Juanma Barranquero
2006-12-20 10:52                         ` Eli Zaretskii
2006-12-20 11:06                           ` Juanma Barranquero
2006-12-20 21:41                         ` Stefan Monnier
2006-12-20 23:13                           ` Juanma Barranquero
2006-12-21 22:47                             ` Stefan Monnier
2006-12-21 22:56                               ` Juanma Barranquero
2006-12-21 23:31                                 ` Stefan Monnier
2006-12-21 23:13                               ` Lennart Borgman
2006-12-22 21:48                                 ` Stefan Monnier [this message]
2006-12-23  0:33                                   ` Lennart Borgman
2006-12-21  1:02                         ` Lennart Borgman
2006-12-21 10:03                           ` Lennart Borgman
2006-12-04  5:15             ` Richard Stallman
2006-12-04  8:55               ` Kim F. Storm
2006-12-05  1:45                 ` Richard Stallman
2006-12-20 11:22 LENNART BORGMAN
2006-12-20 14:36 ` Kim F. Storm
2006-12-21 11:52 ` Jason Rumney

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=jwvtzznbo0u.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.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).