From: Bob Hepple <bob.hepple@gmail.com>
To: rgm@gnu.org, 33158@debbugs.gnu.org
Subject: bug#33158: 26.1; some vc operations on 'src' files result in 'src: -- is not registered'
Date: Sat, 27 Oct 2018 09:20:17 +1000 [thread overview]
Message-ID: <CAHzpm2j0X2ozgX9sON+1PpR7X7pttMLG8QhVZavqN2o+1CLheQ@mail.gmail.com> (raw)
In-Reply-To: <p6h8h8z5pp.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Odd indeed!
I'm using the most recent version 1.18 downloaded from gitlab e6acd942
Anyway:
$ src cat 2 tamborine.org # works fine but:
$ src cat 2 -- tamborine.org
src: -- is not registered
... so it looks like a disconnect between the 'src' doco and reality ie a
bug in 'src'. I'll raise a bug report with esr.
'src' does not use 'getopt' nor 'optparse' etc - it parses the command line
arguments itself. So I _think_ it's falling into one of the nasty edge
cases inherent in that approach.
I have my workaround - I guess it's up to you if you want to apply it in
vc-src.el for other users until esr fixes 'src'.
Thanks for your hard work on my favourite editor (since the mid-eighties!)
Cheers
Bob
On Sat, 27 Oct 2018 at 08:46, Glenn Morris <rgm@gnu.org> wrote:
>
> This is odd since the "--" was added 4 years ago in baab20d by src's
> author,
> and http://www.catb.org/~esr/src/src.html says:
>
> The token "--" tells the command-line interpreter that subcommands,
> switches, and revision-specs are done - everything after it is a
> filename, even if it looks like a subcommand or revision number.
>
>
[-- Attachment #2: Type: text/html, Size: 1962 bytes --]
next prev parent reply other threads:[~2018-10-26 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 0:22 bug#33158: 26.1; some vc operations on 'src' files result in 'src: -- is not registered' Bob Hepple
2018-10-26 22:46 ` Glenn Morris
2018-10-26 23:20 ` Bob Hepple [this message]
2018-10-27 11:35 ` Bob Hepple
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHzpm2j0X2ozgX9sON+1PpR7X7pttMLG8QhVZavqN2o+1CLheQ@mail.gmail.com \
--to=bob.hepple@gmail.com \
--cc=33158@debbugs.gnu.org \
--cc=rgm@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).