yaz-3.0.4 | yaz-client | how is .yazclientrc supported?

Dear list members,

I've just compiled and installed yaz-3.0.4 on Solaris 10.
This is my
first update for at least a year and something significant
seems to
have changed, though I can't find mention in any of the
documentation.

When invoked yaz-client-3.0.4 seems to ignore the
.yazclientrc file in
the current directory. In the past I have found this file
very useful
for scripting queries. Is it now obsolete, or do I now need
to refer to
it explicitly on the command line? Or is something amiss?


Best regards,

 Richard Mahoney


-- 
Richard MAHONEY | internet: http://indica-et-buddh
ica.org/
Littledene      | telephone/telefax (man.): +64 3 312 1699
Bay Road        | cellular: +64 27 482 9986
OXFORD, NZ      | email: r.mahoneyindica-et-buddhica.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Indica et Buddhica: Materials for Indology and Buddhology
Repositorium: http://in
dica-et-buddhica.org/repositorium/
Philologica: http://ind
ica-et-buddhica.org/philologica/
Subscriptions: http://s
ubscriptions.indica-et-buddhica.org/


_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list

Richard MAHONEY wrote:
> Dear list members,
> 
> I've just compiled and installed yaz-3.0.4 on Solaris
10. This is my
> first update for at least a year and something
significant seems to
> have changed, though I can't find mention in any of the
documentation.
> 
> When invoked yaz-client-3.0.4 seems to ignore the
.yazclientrc file in
> the current directory. In the past I have found this
file very useful
> for scripting queries. Is it now obsolete, or do I now
need to refer to
> it explicitly on the command line? Or is something
amiss?
I can see that the client code in versions 2.1.50 and later
only reads 
~/yazclientrc . We'll ensure next version reads from current
directory 
again. But there is one thing that nags - at least - me. If
yaz-client 
is started from ~ (i.e. HOME) then it will read .yazclientrc
twice. So 
my suggestion is that yaz-client does the following
instead:

reads .yazclientrc current directory. Failing that (does not
exist), it 
reads from ~/.yazclientrc . Thus we avoid reading
.yazclientrc twice.

Thanks for bringing this to our attention.

/ Adam

> 
> 
> Best regards,
> 
>  Richard Mahoney
> 
> 


_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list

On Sun, 2007-06-03 at 19:47, Adam Dickmeiss wrote:
> Richard MAHONEY wrote:
> > Dear list members,
> > 
> > I've just compiled and installed yaz-3.0.4 on
Solaris 10. This is my
> > first update for at least a year and something
significant seems to
> > have changed, though I can't find mention in any
of the documentation.
> > 
> > When invoked yaz-client-3.0.4 seems to ignore the
.yazclientrc file in
> > the current directory. In the past I have found
this file very useful
> > for scripting queries. Is it now obsolete, or do I
now need to refer to
> > it explicitly on the command line? Or is something
amiss?
> I can see that the client code in versions 2.1.50 and
later only reads 
> ~/yazclientrc . We'll ensure next version reads from
current directory 
> again. But there is one thing that nags - at least -
me. If yaz-client 
> is started from ~ (i.e. HOME) then it will read
.yazclientrc twice. So 
> my suggestion is that yaz-client does the following
instead:
> 
> reads .yazclientrc current directory. Failing that
(does not exist), it 
> reads from ~/.yazclientrc . Thus we avoid reading
.yazclientrc twice.
> 
> Thanks for bringing this to our attention.
> 
> / Adam

Adam, thanks for indicating where things changed. For my
present
purposes I'll downgrade the version I am using to 2.1.48,
upgrading
again once the new version becomes available.

Your revised yaz-client start up behaviour definitely sounds
like an
improvement and would be most welcome. In addition, could I
make a
suggestion of my own? On startup would it be possible for
yaz-client to
read:

 i.) a script file referenced by `-f script_file' (same
switch as sed);
and failing that

 ii.) a .yazclientrc file in current directory; and failing
that

 iii.) a .yazclientrc file in HOME directory.


I would find the first option especially useful for
scripting queries.
The `f' switch seems to be available at the moment and in
some ways
complements the present `c' (CCL) and `q' (CQL) switches.
Would such an
addition be trivial or acceptable?

I look forward to your comments.


Kind regards,

 Richard 



-- 
Richard MAHONEY | internet: http://indica-et-buddh
ica.org/
Littledene      | telephone/telefax (man.): +64 3 312 1699
Bay Road        | cellular: +64 27 482 9986
OXFORD, NZ      | email: r.mahoneyindica-et-buddhica.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Indica et Buddhica: Materials for Indology and Buddhology
Repositorium: http://in
dica-et-buddhica.org/repositorium/
Philologica: http://ind
ica-et-buddhica.org/philologica/
Subscriptions: http://s
ubscriptions.indica-et-buddhica.org/


_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list

Richard MAHONEY wrote:
> On Sun, 2007-06-03 at 19:47, Adam Dickmeiss wrote:
>> Richard MAHONEY wrote:
>>> Dear list members,
>>>
>>> I've just compiled and installed yaz-3.0.4 on
Solaris 10. This is my
>>> first update for at least a year and something
significant seems to
>>> have changed, though I can't find mention in
any of the documentation.
>>>
>>> When invoked yaz-client-3.0.4 seems to ignore
the .yazclientrc file in
>>> the current directory. In the past I have found
this file very useful
>>> for scripting queries. Is it now obsolete, or
do I now need to refer to
>>> it explicitly on the command line? Or is
something amiss?
>> I can see that the client code in versions 2.1.50
and later only reads 
>> ~/yazclientrc . We'll ensure next version reads
from current directory 
>> again. But there is one thing that nags - at least
- me. If yaz-client 
>> is started from ~ (i.e. HOME) then it will read
.yazclientrc twice. So 
>> my suggestion is that yaz-client does the following
instead:
>>
>> reads .yazclientrc current directory. Failing that
(does not exist), it 
>> reads from ~/.yazclientrc . Thus we avoid reading
.yazclientrc twice.
>>
>> Thanks for bringing this to our attention.
>>
>> / Adam
> 
> Adam, thanks for indicating where things changed. For
my present
> purposes I'll downgrade the version I am using to
2.1.48, upgrading
> again once the new version becomes available.
> 
> Your revised yaz-client start up behaviour definitely
sounds like an
> improvement and would be most welcome. In addition,
could I make a
> suggestion of my own? On startup would it be possible
for yaz-client to
> read:
> 
>  i.) a script file referenced by `-f script_file' (same
switch as sed);
> and failing that
> 
>  ii.) a .yazclientrc file in current directory; and
failing that
> 
>  iii.) a .yazclientrc file in HOME directory.
> 
> 
> I would find the first option especially useful for
scripting queries.
> The `f' switch seems to be available at the moment and
in some ways
> complements the present `c' (CCL) and `q' (CQL)
switches. Would such an
> addition be trivial or acceptable?

You got it.

/ Adam

> I look forward to your comments.
> 
> 
> Kind regards,
> 
>  Richard 
> 
> 
> 


_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list

Richard MAHONEY wrote:

> Your revised yaz-client start up behaviour definitely
sounds like an
> improvement and would be most welcome. In addition,
could I make a
> suggestion of my own? On startup would it be possible
for yaz-client to
> read:
> 
>  i.) a script file referenced by `-f script_file' (same
switch as sed);
> and failing that
> 
>  ii.) a .yazclientrc file in current directory; and
failing that
> 
>  iii.) a .yazclientrc file in HOME directory.

My 2 cents, although I haven't used this feature with yaz
just yet:
.foorc files are generally used to set common options for
program foo,
not to exec arbitrary scripts in. Therefore I'd suggest:

* to first read and exec ./.yazclientrc | ~/.yazclientrc,
which set
options like format, elementsetnames, querytype, you know
the lot;

* and then exec any commands in a -f script

Makes sense?

/Roel

--
Roel de Cock
Programmer
Technical Knowledge Center of Denmark DTV
Anker Engelunds Vej 1, DK-2800 Lyngby, Denmark
+45 4525 7245 (work)  +45 2615 2650 (private, mobile)
http://www.roeland.dk

_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list

Roel de Cock wrote:
> Richard MAHONEY wrote:
> 
>> Your revised yaz-client start up behaviour
definitely sounds like an
>> improvement and would be most welcome. In addition,
could I make a
>> suggestion of my own? On startup would it be
possible for yaz-client to
>> read:
>>
>>  i.) a script file referenced by `-f script_file'
(same switch as sed);
>> and failing that
>>
>>  ii.) a .yazclientrc file in current directory; and
failing that
>>
>>  iii.) a .yazclientrc file in HOME directory.
> 
> My 2 cents, although I haven't used this feature with
yaz just yet:
> .foorc files are generally used to set common options
for program foo,
> not to exec arbitrary scripts in. Therefore I'd
suggest:
> 
> * to first read and exec ./.yazclientrc |
~/.yazclientrc, which set
> options like format, elementsetnames, querytype, you
know the lot;
> 
> * and then exec any commands in a -f script
> 
> Makes sense?

I slightly prefer the original proposal.. mostly because
that's how it's 
implemented now 

Also, if yaz-client would always read the .yazclientrc file,
then 
suddenly we need an option to prevent that.

As it is now, we can prevent that from happening with:
   yaz-client -f/dev/null ..

-f semantics are similar to
   --rcfile file
for bash, which makes bash read file instead of .bashrc /
.bash.bashrc .

Again, I don't have strong feelings either way.

/ Adam

> 
> /Roel
> 
> --
> Roel de Cock
> Programmer
> Technical Knowledge Center of Denmark DTV
> Anker Engelunds Vej 1, DK-2800 Lyngby, Denmark
> +45 4525 7245 (work)  +45 2615 2650 (private, mobile)
> http://www.roeland.dk
> 
> _______________________________________________
> Yazlist mailing list
> Yazlistlists.indexdata.dk
> http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list
> 
> 


_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list