[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Editor and sensible-editor



Hi Brock :)

put this in your .bashrc and/or .bash_profile:

export EDITOR=pico

and see what happens.

Meanwhile, here's something for you to ignore if the above works:

First, the bad news :) If you're not a developer, you don't have a vote, and
you shouldn't be putting your posts in official terms as you are. You say
you don't have a key; guess what? you need a key in order to vote :)

Now, the good news :) It's not hard to become a developer. Then you will have
a vote and all that stuff :)

More bad news dept: It seems you don't agree with the debian social
contract... or do you? Give it a read, then read the license to pine.
Pine is -non-free-, and from what we know of the license and the licenseor,
there have been guesses made that it never will be freed.

So you know: you -have- to agree with the debian social contract to be 
considered for developer status. Developer status is -necessary- to have
a vote.

Debian has a "main" distribution, which consists of only software that is
DFSG-free. Ideally, no package in main should originate package relations
with packages that are not free. Exceptions to this include parts of a whole
split into free and non-free parts, like gimp and gimp-non-free.

You are suggesting that pico be actually mentioned in the sensible-editor
script (q: is this in main?) If it is in main, it doesn't make sense that 
it should.

Also, as pointed out earlier, you can set your environment variables to 
whatever editor suits you, pico would work -fine- in that it supports it-
self by allowing the syntax "pico <filename>" syntax.

Hence, it does not make sense that you should be disagreeing with a proposal
made to create an abstraction to any editor. Specifically, if you think
that this proposal does not support pico, then you do not understand shell
scripting in this area. That is very easy for you to fix, however: info bash
is definitive and tutorial simultaneously.

Keep posting your opinions tho. Please don't use language that would suggest
that you are applying clout, because you will confuse us (well, me anyways)
into checking into your debian credentials, or lack thereof (as turned out in
this case). 

-Jim



Reply to: