zsh-workers
 help / color / mirror / code / Atom feed
From: Richard Hartmann <richih.mailinglist@gmail.com>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: zsh-workers@zsh.org
Subject: Re: vcs_info and locales
Date: Wed, 19 May 2010 12:07:14 +0200	[thread overview]
Message-ID: <AANLkTino3InBI8XAu28UIwP6jRH0yAaiEpwyxp2JPzmi@mail.gmail.com> (raw)
In-Reply-To: <8739yjoc84.fsf@ft.bewatermyfriend.org>

On Sun, Apr 25, 2010 at 16:09, Frank Terbeck <ft@bewatermyfriend.org> wrote:

> Probably true. Although, I'd expect programs you can use for scripting
> to use untempered byte sequences. But then, where is the boundary for
> programs that are used for scripting and pure user-interface programs...
> `svn info' is probably a pretty blurry example already.

While fixing locales is a viable workaround, the root cause is that svn
is not able to present its information in a machine-readable way.

Would it be worthwhile to try and lobby svn etc to support something
like --output text; --output xml (yah, yah, I know) etc?

Everything else feels like a kludge.


Richard

PS: I seem to remember that one or two VCS have something like
this, but that is _very_ dim.


  parent reply	other threads:[~2010-05-19 10:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-24 21:40 François Gannaz
2010-04-25  8:38 ` Frank Terbeck
2010-04-25 10:36   ` François Gannaz
2010-04-25 13:19   ` Phil Pennock
2010-04-25 14:09     ` Frank Terbeck
2010-04-25 14:29       ` Frank Terbeck
2010-05-19 10:07       ` Richard Hartmann [this message]
2010-05-19 11:50         ` François Gannaz
2010-05-19 12:03           ` Richard Hartmann
2010-04-25 19:09     ` François Gannaz
2010-04-26  0:29       ` Phil Pennock
2010-04-26  6:36         ` Frank Terbeck
2010-04-26  8:56           ` François Gannaz
2010-04-26 19:07             ` Frank Terbeck

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=AANLkTino3InBI8XAu28UIwP6jRH0yAaiEpwyxp2JPzmi@mail.gmail.com \
    --to=richih.mailinglist@gmail.com \
    --cc=ft@bewatermyfriend.org \
    --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).