On Mon, Aug 30, 2010 at 11:33 PM, Greg Wooledge wrote:
> On Mon, Aug 30, 2010 at 11:25:00PM +1000, Jon Seymour wrote:
>> I am working on an extension to git, and need to store a list of shell
>> files that can be used to extend the capabilities of the command I am
>> writing. Most of the time, a v
On 08/30/2010 08:57 AM, Eric Blake wrote:
[adding bug-bash]
On 08/29/2010 08:48 AM, Ralf Wildenhues wrote:
With Solaris 10 sh (and others):
cat<
Ouch. New one to me. ksh, zsh, and dash do not echo the quotes, so I'm
thinking it may be a bash bug; hence the cc.
Sorry about that; I read my res
[adding bug-bash]
On 08/29/2010 08:48 AM, Ralf Wildenhues wrote:
With Solaris 10 sh (and others):
cat<
Ouch. New one to me. ksh, zsh, and dash do not echo the quotes, so I'm
thinking it may be a bash bug; hence the cc.
Eric, did you have this in your recent autoconf.texi additions alread
Hi Greg,
I've already read your Wiki, but gettext complains alot about $"string",
therefore I wanted to try the
new syntax. I've read about eval_gettext, but it's not working correctly a) the
pot does not contain all
strings, b) the translated strings won't show up. Generally I may use $"string"
On Mon, Aug 30, 2010 at 7:30 PM, Pierre Gaston wrote:
> On Mon, Aug 30, 2010 at 1:35 PM, Clark J. Wang wrote:
> > The Bash manual says:
> >
> > "A double-quoted string preceded by a dollar sign ($) will cause the
> string
> > to be translated according to the current locale. If the current local
On Mon, Aug 30, 2010 at 11:25:00PM +1000, Jon Seymour wrote:
> I am working on an extension to git, and need to store a list of shell
> files that can be used to extend the capabilities of the command I am
> writing. Most of the time, a variable of the form:
>
> GIT_EXTRA_CONDITION_LIBS="libA.sh l
Chris, Andrej and Greg,
Thanks for your helpful replies.
You are quite correct on pointing out that the solution does depend on
how it is to be used
To provide more context:
I am working on an extension to git, and need to store a list of shell
files that can be used to extend the capabilities
On Sun, Aug 29, 2010 at 08:31:32PM +0200, Christopher Roy Bratusek wrote:
> Hi all,
>
> I'm struggling around at translating a shell script. Well I've set it up, the
> pot file
> contains all strings, the german .po file is finished, but: the strings won't
> show up...
Everything I know about l
On Sun, Aug 29, 2010 at 04:07:23AM -0400, Chris F.A. Johnson wrote:
> On Sun, 29 Aug 2010, Jon Seymour wrote:
>
> >This isn't strictly a bash question, and I'd prefer a POSIX-only
> >solution if possible
> >Suppose I need to encode a list of filenames in a variable
POSIX shells won't have arrays
On Mon, 30 Aug 2010 14:30:45 +0300 Pierre Gaston
wrote:
> On Mon, Aug 30, 2010 at 1:35 PM, Clark J. Wang wrote:
> > The Bash manual says:
> >
> > "A double-quoted string preceded by a dollar sign ($) will cause the
> > string to be translated according to the current locale. If the
> > current
On Mon, 30 Aug 2010 18:35:46 +0800
"Clark J. Wang" wrote:
> The Bash manual says:
>
> "A double-quoted string preceded by a dollar sign ($) will cause the
> string to be translated according to the current locale. If the current
> locale is C or POSIX, the dollar sign is ignored. If the stri
On Mon, Aug 30, 2010 at 1:35 PM, Clark J. Wang wrote:
> The Bash manual says:
>
> "A double-quoted string preceded by a dollar sign ($) will cause the string
> to be translated according to the current locale. If the current locale is
> C or POSIX, the dollar sign is ignored. If the string is
The Bash manual says:
"A double-quoted string preceded by a dollar sign ($) will cause the string
to be translated according to the current locale. If the current locale is
C or POSIX, the dollar sign is ignored. If the string is translated and
replaced, the replacement is double-quoted."
Any
13 matches
Mail list logo
