From: "Oliver Večerník" <ov@vecernik.at>
To: emacs-orgmode@gnu.org
Subject: Re: diff in `src' blocks
Date: Mon, 13 May 2013 11:29:20 +0200 [thread overview]
Message-ID: <87y5bjns7j.fsf@kerstf.org> (raw)
In-Reply-To: loom.20130513T103111-542@post.gmane.org
>> Figured out myself, sorry for the noise. It has to do with the exit
>> status of the `diff', which is 1 if the files are different. So I use
>> the pipe through `cat'.
>
> Useless use of cat...
At least the return status is zero. But I agree with you, a colon is
better here. This is my first use of a `:' btw. I never had case
before.
--
Thanks,
Oliver
next prev parent reply other threads:[~2013-05-13 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 7:33 diff in `src' blocks Oliver Večerník
2013-05-13 8:07 ` Oliver Večerník
2013-05-13 8:32 ` Achim Gratz
2013-05-13 9:29 ` Oliver Večerník [this message]
2013-05-13 8:30 ` Achim Gratz
2013-05-13 17:59 ` Achim Gratz
2013-05-13 19:23 ` Samuel Wales
2013-05-14 9:07 ` Michael Brand
2013-05-14 9:12 ` Michael Brand
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5bjns7j.fsf@kerstf.org \
--to=ov@vecernik.at \
--cc=emacs-orgmode@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/org-mode.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).