gEDA-dev: geda naming convention

[Steve Meier]

How does this keep me from not having to know all of the commands that I
would use? Yes it groups them together if the are geda-whatever so tha
if I know which directory to do a search for I can find them as a group
but I still have to know if the are in /usr/bin or /usr/local/bin or
where ever?

I can see how a program like geda-help might help but adding extra
charcters to invoke a command is just to my anoying. Anyone who reads my
diatribes knows how often I type and adding extra characters that in my
perspective have no value are just going to increase my frustration.

Sorry I see no benefit.

Steve M.

Igor2 wrote:
> On Sun, 9 Dec 2007, Steve Meier wrote:
>
>   
>> What?
>>
>> so this would change me from typing
>>
>> gschem top.sch
>>
>> to
>>
>> geda gschem top.sch
>>
>> Well I am far to lazy to do that, though if others want to go ahead. But
>> it makes no scense to me. Also it seems to mush like
>>
>> mother may I gschem top.sch
>>
>>     
>
> /usr/bin/geda could be a simple shell script that parses command line
> arguments and calls the right tool(s) on the old name. This way existing
> makefiles and user habits wouldn't break while we could have a general
> geda command.
>
>
>
> _______________________________________________
> geda-dev mailing list
> geda-dev at moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
>
>