unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: lekktu@gmail.com, 12055@debbugs.gnu.org
Subject: bug#12055: Re: bug#12055: Re: bug#12055: 24.1.50; Characters "á" and "é" are not correctly displayed on a Windows terminal
Date: Sat, 28 Jul 2012 15:30:21 +0300	[thread overview]
Message-ID: <837gtohxuq.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0iueVZcya2TsHhtF1tFvS7FNOQRn6+V79f8MqDSVEZ2rw@mail.gmail.com>

> Date: Sat, 28 Jul 2012 13:55:41 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: lekktu@gmail.com, 12055@debbugs.gnu.org
> 
> This is what I'm trying to do (from an Emacs -Q):
> 1. Copy your patch and paste it in a new Emacs buffer, and save it to
> a file "patch.diff" (with UNIX-type EOL format).
> 2. Go to each hunk and type "C-c C-a".
> 
> This is failing for me in the hunks that begin with:
>   @@ -786,6 +788,11 @@ initialize_w32_display (struct terminal
>   @@ -61,6 +62,15 @@ static INPUT_RECORD *queue_ptr = event_q
>   @@ -80,8 +90,8 @@ fill_queue (BOOL block)
>   @@ -447,26 +452,34 @@ key_event (KEY_EVENT_RECORD *event, stru
> 
> For these hunks, I receive the error message "Can't find the text to patch".

Perhaps your copy/paste procedure didn't preserve the TAB characters,
converting them into spaces instead.  Can "C-c C-a" ignore whitespace
changes?  If not, Patch can, if you use the -l (the letter ell, not
the digit 1) option.





  parent reply	other threads:[~2012-07-28 12:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 12:13 bug#12055: 24.1.50; Characters "á" and "é" are not correctly displayed on a Windows terminal Dani Moncayo
2012-07-26 16:13 ` Eli Zaretskii
2012-07-26 16:24   ` Juanma Barranquero
2012-07-26 16:42     ` bug#12055: " Eli Zaretskii
2012-07-26 16:49       ` Juanma Barranquero
2012-07-26 17:18         ` bug#12055: " Eli Zaretskii
2012-07-26 18:09           ` Eli Zaretskii
2012-07-26 18:42             ` Juanma Barranquero
2012-07-26 18:29           ` Juanma Barranquero
2012-07-26 20:03             ` bug#12055: " Eli Zaretskii
2012-07-26 22:40               ` Dani Moncayo
2012-07-27  6:45                 ` bug#12055: " Eli Zaretskii
2012-07-27  8:35                   ` Dani Moncayo
2012-07-27  9:04                     ` bug#12055: " Eli Zaretskii
2012-07-27 15:12                       ` Eli Zaretskii
2012-07-27 16:46                         ` Jason Rumney
2012-07-27 18:03                           ` Eli Zaretskii
2012-07-27 18:22                             ` Eli Zaretskii
2012-07-27 23:45                         ` Juanma Barranquero
2012-07-28  1:12                         ` Dani Moncayo
2012-07-28  8:04                           ` bug#12055: " Eli Zaretskii
2012-07-28 10:06                             ` Eli Zaretskii
2012-07-28 11:55                               ` Dani Moncayo
2012-07-28 12:23                                 ` bug#12055: " Eli Zaretskii
2012-07-28 12:49                                   ` Dani Moncayo
2012-07-28 15:02                                     ` bug#12055: " Eli Zaretskii
2012-07-28 12:30                                 ` Eli Zaretskii [this message]
2012-07-28 13:57                               ` Dani Moncayo
2012-07-28 16:07                                 ` Juanma Barranquero
2012-07-28 16:12                                   ` Dani Moncayo
2012-07-28 16:11                               ` Juanma Barranquero
2012-07-28 16:44                                 ` bug#12055: " Eli Zaretskii
2012-07-28 17:01                                   ` Eli Zaretskii
2012-07-26 16:44     ` Dani Moncayo
2012-07-28 14:12 ` Dani Moncayo
2012-07-28 15:01   ` bug#12055: " Eli Zaretskii
2012-07-28 15:23     ` Dani Moncayo
2012-07-28 15:34       ` Dani Moncayo
2012-07-28 16:27         ` bug#12055: " Eli Zaretskii
2012-07-28 15:35       ` Eli Zaretskii
2012-07-28 15:46         ` Dani Moncayo

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=837gtohxuq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12055@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --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).