starred/frontail

Fork 0

mirror of https://github.com/mthenw/frontail.git synced 2026-04-26 02:05:57 +03:00

[GH-ISSUE #53] README lists -h option as alias for both --help and --host #36

New issue

Closed

opened 2026-03-03 16:03:52 +03:00 by kerem · 11 comments

kerem commented

2026-03-03 16:03:52 +03:00

Owner

Originally created by @ChristianWilkie on GitHub (Sep 15, 2015).
Original GitHub issue: https://github.com/mthenw/frontail/issues/53

In the project README under Usage the option -h is listed as an alias for both --help and --host. When I run frontail -h it seems to actually refer to --host:

error: option `-h, --host <host>' argument missing

Also, running frontail --help lists the same thing:

Usage: frontail [options] [file ...]

Options:

-h, --help                    output usage information
...
-h, --host <host>             listening host, default 0.0.0.0
...

Anyway, not a huge deal, but I just thought I'd mention it.

Originally created by @ChristianWilkie on GitHub (Sep 15, 2015). Original GitHub issue: https://github.com/mthenw/frontail/issues/53 In the project README under Usage the option `-h` is listed as an alias for both `--help` and `--host`. When I run `frontail -h` it seems to actually refer to `--host`: ``` error: option `-h, --host <host>' argument missing ``` Also, running `frontail --help` lists the same thing: ``` Usage: frontail [options] [file ...] Options: -h, --help output usage information ... -h, --host <host> listening host, default 0.0.0.0 ... ``` Anyway, not a huge deal, but I just thought I'd mention it.

kerem

2026-03-03 16:03:52 +03:00

closed this issue
added the
bug

accepted
labels

kerem commented

2026-03-03 16:03:53 +03:00

Author

Owner

@mthenw commented on GitHub (Sep 16, 2015):

Thanks for reporting. It's not a big deal, but based on my quick research it won't be easy. I need to replace options parser (commander) with other library.

@mthenw commented on GitHub (Sep 16, 2015): Thanks for reporting. It's not a big deal, but based on my quick research it won't be easy. I need to replace options parser (commander) with other library.

kerem commented

2026-03-03 16:03:53 +03:00

Author

Owner

@Spown commented on GitHub (May 5, 2016):

yeah... that, or just remove "-h" from "-h, --help output usage information" both in the readme and the referance. so only "--help" would remain, duh

@Spown commented on GitHub (May 5, 2016): yeah... that, or just remove "-h" from "-h, --help output usage information" both in the readme and the referance. so only "--help" would remain, duh

kerem commented

2026-03-03 16:03:54 +03:00

Author

Owner

@mthenw commented on GitHub (May 5, 2016):

@Spown wanna contribute? :)

@mthenw commented on GitHub (May 5, 2016): @Spown wanna contribute? :)

kerem commented

2026-03-03 16:03:54 +03:00

Author

Owner

@Spown commented on GitHub (May 5, 2016):

well, I already forked it. right now I'm trying to compose a buildable version for node 4, since socket.io 0.9 you are using is so old it won't even compile. and the node-temp in tests doesn't work either. If I mange to make it run - I'll make a pull request.

@Spown commented on GitHub (May 5, 2016): well, I already forked it. right now I'm trying to compose a buildable version for node 4, since socket.io 0.9 you are using is so old it won't even compile. and the node-temp in tests doesn't work either. If I mange to make it run - I'll make a pull request.

kerem commented

2026-03-03 16:03:54 +03:00

Author

Owner

@mthenw commented on GitHub (May 5, 2016):

Yeah, there is a bunch of other stuff that doesn't work on Node 4. I will try to fix that today, so you can work only on this fix.

@mthenw commented on GitHub (May 5, 2016): Yeah, there is a bunch of other stuff that doesn't work on Node 4. I will try to fix that today, so you can work only on this fix.

kerem commented

2026-03-03 16:03:54 +03:00

Author

Owner

@mthenw commented on GitHub (May 5, 2016):

@Spown push to master version working with Node v4. There is no problem with socket.io (TravisCI can confirm).

@mthenw commented on GitHub (May 5, 2016): @Spown push to master version working with Node v4. There is no problem with socket.io (TravisCI can confirm).

kerem commented

2026-03-03 16:03:54 +03:00

Author

Owner

@Spown commented on GitHub (May 5, 2016):

funny thing, node-temp runs in node 4.2.2 under linux, but not in windows (mayhaps, the same goes for socket.io)

https://travis-ci.org/Spown/frontail/jobs/127997186

  49 passing (889ms)
  3 failing

  1) tail calls event line if new line appear in file:
     Uncaught Error: spawn tail ENOENT
      at exports._errnoException (util.js:874:11)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
      at onErrorNT (internal/child_process.js:344:16)

  2) tail buffers lines on start:
     Uncaught Error: spawn tail ENOENT
      at exports._errnoException (util.js:874:11)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
      at onErrorNT (internal/child_process.js:344:16)

  3) tail buffers no lines on start by default:
     Uncaught Error: spawn tail ENOENT
      at exports._errnoException (util.js:874:11)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
      at onErrorNT (internal/child_process.js:344:16)

@Spown commented on GitHub (May 5, 2016): funny thing, node-temp runs in node 4.2.2 under linux, but not in windows (mayhaps, the same goes for socket.io) https://travis-ci.org/Spown/frontail/jobs/127997186 ``` 49 passing (889ms) 3 failing 1) tail calls event line if new line appear in file: Uncaught Error: spawn tail ENOENT at exports._errnoException (util.js:874:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32) at onErrorNT (internal/child_process.js:344:16) 2) tail buffers lines on start: Uncaught Error: spawn tail ENOENT at exports._errnoException (util.js:874:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32) at onErrorNT (internal/child_process.js:344:16) 3) tail buffers no lines on start by default: Uncaught Error: spawn tail ENOENT at exports._errnoException (util.js:874:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32) at onErrorNT (internal/child_process.js:344:16) ```

kerem commented

2026-03-03 16:03:54 +03:00

Author

Owner

@Spown commented on GitHub (May 5, 2016):

the thing is I really need to make it run in windows, because I need to watch for a remote file on an Openshift server (where I'm not able to run multiple apps on different ports, afaik). So if I unable - I kinda have no use for it...

@Spown commented on GitHub (May 5, 2016): the thing is I really need to make it run in windows, because I need to watch for a remote file on an Openshift server (where I'm not able to run multiple apps on different ports, afaik). So if I unable - I kinda have no use for it...

kerem commented

2026-03-03 16:03:54 +03:00

Author

Owner

@Spown commented on GitHub (May 5, 2016):

it would be really cool, if this module had an express middleware version though

@Spown commented on GitHub (May 5, 2016): it would be really cool, if this module had an express middleware version though

kerem commented

2026-03-03 16:03:54 +03:00

Author

Owner

@mthenw commented on GitHub (May 5, 2016):

There is newer version on temp. You could try using that.

@mthenw commented on GitHub (May 5, 2016): There is newer version on `temp`. You could try using that.

kerem commented

2026-03-03 16:03:54 +03:00

Author

Owner

@Spown commented on GitHub (May 5, 2016):

yeah, I just found another trailing solution, sorry. still according to https://www.npmjs.com/package/commander#helpcb you don't need to replace options parser - just take out one "-h" from the help text.

@Spown commented on GitHub (May 5, 2016): yeah, I just found another trailing solution, sorry. still according to https://www.npmjs.com/package/commander#helpcb you don't need to replace options parser - just take out one "-h" from the help text.

kerem referenced this issue

2026-03-03 16:05:53 +03:00

[PR #36] [MERGED] --ui-highlight #183