From: "Lawrence Velázquez" <larryv@macports.org>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-workers@zsh.org
Subject: Re: trouble with debugging binary
Date: Sun, 23 Nov 2014 02:58:44 -0500 [thread overview]
Message-ID: <089E69C3-7394-4EB6-A321-D542D881C60E@macports.org> (raw)
In-Reply-To: <5470BE8D.5030009@eastlink.ca>
On Nov 22, 2014, at 11:49 AM, Ray Andrews <rayandrews@eastlink.ca> wrote:
> On 11/21/2014 09:43 PM, Bart Schaefer wrote:
>> break;
>> + case WC_AUTOFN:
>> + taddstr("builtin autoload -X");
>> + stack = 1;
>> + break;
>>
> Yoku dekimashita Sensei
>
> These patches, they don't look like normal diffs, is it a git
> exclusive? Are they applied by some git subcommand?
The "unified" format is quite common. I personally have a hard time reading diffs in other formats.
https://en.wikipedia.org/wiki/Diff_utility#Unified_format
vq
next prev parent reply other threads:[~2014-11-23 7:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 21:36 PATCH: key bindings, fixes, docs, tests for vi stuff Oliver Kiddle
2014-11-18 8:04 ` Jun T.
2014-11-19 8:48 ` Oliver Kiddle
2014-11-19 15:35 ` Ray Andrews
2014-11-21 0:01 ` Oliver Kiddle
2014-11-21 0:49 ` Bart Schaefer
2014-11-21 1:10 ` Ray Andrews
2014-11-21 5:53 ` Bart Schaefer
2014-11-21 10:35 ` Oliver Kiddle
2014-11-22 6:59 ` Bart Schaefer
2014-12-12 16:47 ` Oliver Kiddle
2014-11-21 1:15 ` Ray Andrews
2014-11-21 2:20 ` Mikael Magnusson
2014-11-21 2:38 ` Ray Andrews
2014-11-21 6:23 ` Bart Schaefer
2014-11-21 17:28 ` trouble with debugging binary Ray Andrews
2014-11-22 4:45 ` Bart Schaefer
2014-11-22 5:27 ` Ray Andrews
2014-11-22 5:43 ` Bart Schaefer
2014-11-22 16:49 ` Ray Andrews
2014-11-22 22:35 ` Bart Schaefer
2014-11-23 7:58 ` Lawrence Velázquez [this message]
2014-11-23 16:22 ` Ray Andrews
2014-11-23 18:12 ` Mikael Magnusson
2014-11-23 18:42 ` Ray Andrews
2014-11-23 19:01 ` Mikael Magnusson
2014-11-23 22:30 ` Ray Andrews
2014-11-21 15:20 ` PATCH: key bindings, fixes, docs, tests for vi stuff Jun T.
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=089E69C3-7394-4EB6-A321-D542D881C60E@macports.org \
--to=larryv@macports.org \
--cc=rayandrews@eastlink.ca \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).