Re: 'bashbug behavior and doc problem(s)...

[Linda Walsh]

Greg Wooledge wrote:
> On Mon, Feb 15, 2016 at 10:31:24AM -0800, LA Walsh wrote:
>   
> > Ended up looking at manpage, where it says under "ENVIRONMENT":
> >
> >  EDITOR Specifies the preferred editor. If EDITOR is not set, bashbug
> >         defaults to emacs.
> >     
>
> This is not correct (probably it used to be).  bashbug defaults to
> /usr/bin/editor if that exists, then ce, then emacs (it looks in
> multiple places, but doesn't check the PATH variable), then jove,
> then finally vi.
>   
wow...
> I'm guessing your operating system has a /usr/bin/editor symlink
> that points to gvim.
>   
nep....
>  whence editor ce emacs jove vi
-bash: type: editor: not found
-bash: type: ce: not found
emacs is /usr/bin/emacs
emacs is /usr/bin/X11/emacs
-bash: type: jove: not found
vi is /usr/bin/vi
vi is /bin/vi
vi is /usr/bin/X11/vi
>  ll {,/usr}/bin/{editor,ce,emacs,jove,vi}
ls: cannot access /bin/editor: No such file or directory
ls: cannot access /bin/ce: No such file or directory
ls: cannot access /bin/emacs: No such file or directory
ls: cannot access /bin/jove: No such file or directory
ls: cannot access /usr/bin/editor: No such file or directory
ls: cannot access /usr/bin/ce: No such file or directory
ls: cannot access /usr/bin/jove: No such file or directory
lrwxrwxrwx  1  3 May 27  2015 /bin/vi -> vim*
-rwxrwxr-x+ 2 28 Sep  3  2011 /usr/bin/emacs*
lrwxrwxrwx  1  8 May 27  2015 /usr/bin/vi -> /bin/vim*
---

It would find 'emacs' first, hmmm 28 bytes? ah HA!:
>  more /usr/bin/emacs
#!/bin/bash
exec gvim "$@"

Well, at least that makes some sense...still...
the idea of using your cmdline editing mode to select
a default seems a bit more userfriendly, IMO.... ;-)