If the problem is that funced and funcedit are describing the same
action, then what would make the most sense to use an options to
change which editor should open. A universal variable could choose the
default could also choose the default.  This is discoverable by having
it documented along with funced.

E.g.
-x   graphical editor
-t   text based editor (e.g. use $EDITOR)
-i   internal read based editor
-e EDITOR   explicitly specified editor
set -U fish_editor preferred_editor

A similar approach could be taken for the browser for help.

I didn't put too much thought into the options to use, so feel free to
choose different ones if you implement it this way.

On Wed, Nov 24, 2010 at 8:22 PM, James Bowlin <[email protected]> wrote:
> On Thu, Nov 25, 2010 at 11:29 AM, Christopher Nilsson said:
>> Just may want to take care with the name:  'funcedit' is pretty close
>> to the existing 'funced' function.  I'm at work right now, where all
>> creativity has been sucked out of me ;) , so I've no suggestions for
>> something to use instead.
>
> My thought was that since they both do the same thing it is good to
> have the one with the external editor just have an extension of the
> shorter name.  This is easy for me to remember and helps with discovery
> (I think).  I'm open to changing the name if someone has a better idea
> down the pike.  Maybe funced-external would make everyone happy.  I will
> try that.  If I keep the vim specific one, I'll change it to funced-vim.
> Again, I'm open to suggestions regarding all of the above.
>
>
> An easy way to deal with the $BROWSER variable in help.fish is to
> simply pre-pend it to the list of graphical browsers and also prepend
> it to the list of text browsers if it is a known text browser, otherwise
> stick it at the end of the list of text browsers.
>
> Thus $BROWSER will be the default in graphical mode but we can fall back
> to other browsers if we can't find it.  In text mode $BROWSER becomes
> the default only if it is a known text browser, otherwise it becomes our
> last resort.  This way, the only way $BROWSER can break help.fish is if
> it points to an existing program that is not a browser.
>
>
> Peace, James
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Fish-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fish-users
>

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users

Reply via email to