comment on

I tried this, and it doesn't work for 'git fetch --tags' for some reason.

My guess is that using this command produces some sort of 'active' output (for want of a better description) in the terminal, and it isn't a static output like you would get from backticks 'ls' or 'ps ax' etc.

Now for some reason, once you run 'git fetch --tags', any other time you run it, there is no output - I don't know how to reset it to test - but maybe try saving the command in a text file chmod 755 gitfetch.sh and then use

my $git = `.\gitfetch.sh`;
[download]

BTW, using 'my $git = `git status`; works:

:~/git/claws/claws$ perl gittest 
What's here? --- On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
  (use "git add <file>..." to include in what will be committed)

    gittest

nothing added to commit but untracked files present (use "git add" to 
+track)
[download]

Nick

In reply to Re^4: Capturing bash output without displaying STOUT in terminal by Linicks
in thread Capturing bash output without displaying STOUT in terminal by edimusrex

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks