Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming > #5027

Re: Suggest a command line syntax

Show all headers | View raw

Richard Heathfield wrote:

> Anyway, assuming that's the general idea, the command line syntax could be
> something like:
> 
> 
> 
> programname -<options> -pairs p1a p1b [p2a p2b [p3a p3b [...]]] filespec

This way it is easy to confuse <filespec> with pairs.

> Options would be, for example, case-insensitivity (-i) and the like. Then
> would come the pairs - the switch '-pairs' might be considered surplus to
> requirements, so feel free to ditch it - and finally there is the file
> specification (if you're on Unix, you can just let globbing happen).
> 
> Alternatively, if there are many pairs, you could put them in a tab-
> separated file, one pair per line, and specify the filename - e.g.
> 
> programname -i -f=swappairs.tsv j*.txt

Hm, maybe to use CSV instead? It allows encoding arbitrary strings including 
comma and tab.

-- 
Victor Porton - http://portonvictor.org

Back to comp.programming | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Suggest a command line syntax Victor Porton <porton@narod.ru> - 2014-12-22 20:10 +0200
  Re: Suggest a command line syntax Richard Heathfield <invalid@see.sig.invalid> - 2014-12-22 18:42 +0000
    Re: Suggest a command line syntax Victor Porton <porton@narod.ru> - 2014-12-22 20:48 +0200
      Re: Suggest a command line syntax Richard Heathfield <invalid@see.sig.invalid> - 2014-12-22 19:44 +0000
  Re: Suggest a command line syntax Kaz Kylheku <kaz@kylheku.com> - 2014-12-22 20:09 +0000
  Re: Suggest a command line syntax Robert Wessel <robertwessel2@yahoo.com> - 2014-12-22 14:46 -0600
    Re: Suggest a command line syntax Kaz Kylheku <kaz@kylheku.com> - 2014-12-22 21:40 +0000

csiph-web