Kartik Kulkarni writes:

> I believe that this bug is too old and I am taking the liberty to
> close it.

Is age (alone) sufficient cause to close a bug?

The current version in Debian unstable seems to be more broken, compared
to what the help text says:

  $ source-highlight --src-lang perl hello
  Processing hello ... created hello.html
  $ source-highlight --src-lang perl --output=STDOUT hello
  Please, use one of the two syntaxes for invocation: 
  source-highlight [OPTIONS]... -i input_file -o output_file
  source-highlight [OPTIONS]... [FILES]...
  $ source-highlight --help | grep -A3 'output=FILENAME'
    -o, --output=FILENAME         Output file (default=stdout, when the third
                                    invocation form is used). If 'STDOUT' is
                                    specified, the output is directed to 
standard
                                    output
  $ source-highlight --version | head -n 1
  GNU Source-highlight 3.1.9 (library: 4:1:0)
  $ 

The --output STDOUT no longer works, despite the help text.

Ah, it is now mandatory to use --input when using --output (that's what
"the third invocation form" is about), it seems:

  $ source-highlight --src-lang perl --output=STDOUT --input=hello
  <!-- Generator: GNU source-highlight 3.1.9
  by Lorenzo Bettini
  http://www.lorenzobettini.it
  http://www.gnu.org/software/src-highlite -->
  <pre><tt><i><font color="#9A1900">#!/usr/bin/perl</font></i>
    [...]
  say <font color="#FF0000">'Hello world'</font><font color="#990000">;</font>
  </tt></pre>
  $ 

And if you use --input and no --output, the behaviour I expected with
just a filename is observed:

  $ source-highlight --src-lang perl --input=hello
  <!-- Generator: GNU source-highlight 3.1.9
  by Lorenzo Bettini
  http://www.lorenzobettini.it
  http://www.gnu.org/software/src-highlite -->
  <pre><tt><i><font color="#9A1900">#!/usr/bin/perl</font></i>
    [...]
  say <font color="#FF0000">'Hello world'</font><font color="#990000">;</font>
  </tt></pre>
  $ 

I still think the help text is confusing, but at least now it won't
overwrite a existing file *if* you use --input.

Upstream it seems that this is the expected behaviour:

  "Sat 01 Jun 2019 08:18:17 PM UTC, comment #2: 
   I think this is fixed now
   Tom Tromey <tromey>"

 · http://savannah.gnu.org/support/index.php?106347#comment2

So for that reason I think it is fine to close this bug.

Thanks for taking the time to look at this oldie!


  Best regards,

    Adam

-- 
 "I wonder if you can refuse to inherit the world."         Adam Sjøgren
 "I think if you're born, it's too late."              a...@koldfront.dk

Reply via email to