emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bash script to update - only make when update there?
Date: Tue, 10 Dec 2013 14:31:47 -0500	[thread overview]
Message-ID: <8738m0lcyk.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 52A75EF2.9010502@krugs.de

Rainer M Krug <Rainer@krugs.de> writes:

> On 12/10/13, 16:59 , Nick Dokos wrote:
>> ...
>> Be that as it may, you can try something like this hack (those are
>> backticks around the git pull - it's under the ESC key in the upper
>> left hand corner on most US keyboards but it may be somewhere else
>> on yours):
>>
>> if [ "`git pull`" == "Already up-to-date" ] then echo "Up to date"
>> else make update fi
>
> True - but if git pull does change the message, I have to change it as
> well - I just leave it as it is.
>

Here for your amusement is a way to get around this problem:

if [ "`git pull`" == "`git pull`" ]
then
        echo Up to date
else
        make update
fi

You pay double the cost every time you use it but if they ever *do*
change the message, it's not going to break. But of course, if the shell
ever optimizes the second git pull away, you are back at square one...

With-tongue-firmly-in-cheek-ly yours,
Nick

next prev parent reply	other threads:[~2013-12-10 19:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10  8:44 Bash script to update - only make when update there? Rainer M Krug
2013-12-10 15:59 ` Nick Dokos
2013-12-10 18:35   ` Rainer M Krug
2013-12-10 19:31     ` Nick Dokos [this message]
2013-12-10 19:37       ` Rainer M Krug
2013-12-10 20:50         ` Samuel Wales
2013-12-12  9:00           ` Rainer M Krug
2013-12-13  0:26             ` Suvayu Ali
2013-12-13  8:40               ` Rainer M Krug
2013-12-10 17:00 ` Achim Gratz
2013-12-10 17:12   ` Achim Gratz
2013-12-10 18:36     ` Rainer M Krug

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=8738m0lcyk.fsf@alphaville.bos.redhat.com \
    --to=ndokos@gmail.com \
    --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

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).