From: Petr Baudis <pasky@ucw.cz>
To: Jonas Fonseca <fonseca@diku.dk>
Cc: Dan Holmsand <holmsand@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Add support reading default options from conf file
Date: Thu, 9 Jun 2005 10:32:43 +0200 [thread overview]
Message-ID: <20050609083243.GD29665@pasky.ji.cz> (raw)
In-Reply-To: <20050609010056.GA9084@diku.dk>
Dear diary, on Thu, Jun 09, 2005 at 03:00:56AM CEST, I got a letter
where Jonas Fonseca <fonseca@diku.dk> told me that...
> Reply-To:
> In-Reply-To: <42A754D5.10705@gmail.com>
>
> Dan Holmsand <holmsand@gmail.com> wrote Wed, Jun 08, 2005:
> > - Automatic color if the COGITO_AUTO_COLOR environment variable is set.
>
> [ This has been discussed before. Default arguments. The 'new' cg
> wrapper makes this very easy. Not as smart as your env variable
> handling tho'. ]
>
> The default options are read only for Cogito calls going through the new
> cg wrapper which makes it trivial to 'overwrite' them by just calling
> cg-COMMAMD.
>
> Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
No, this is the wrong way. The 'cg' wrapper must not really do anything
special on its own. It's not a _replacement_ for direct calling of the
cg-scripts, it's just an aid for people who don't want to get used to
it. So please do this in cg-Xlib.
Also, I'd prefer the config file to be something like ~/.cgrc. I want to
reserve the .conf file for something more sophisticated. ;-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
<Espy> be careful, some twit might quote you out of context..
next prev parent reply other threads:[~2005-06-09 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 1:00 [PATCH] Add support reading default options from conf file Jonas Fonseca
2005-06-09 8:32 ` Petr Baudis [this message]
2005-06-11 1:09 ` [PATCH] Read default options from config file Jonas Fonseca
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=20050609083243.GD29665@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=holmsand@gmail.com \
/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.
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).