| 1 |
On Fri, 2 Oct 2009 03:52:24 -0500, forgottenwizard wrote: |
| 2 |
|
| 3 |
> > Nano is not non-existent by default. |
| 4 |
|
| 5 |
> It isn't always on the users sytem. Providing a non-existent default |
| 6 |
> seems quite broken to me. |
| 7 |
|
| 8 |
That's true of every editor, so you have to choose the one that is most |
| 9 |
likely to be there, the one that is installed for the stage tarballs and |
| 10 |
is there unless the user has taken specific steps to remove it. |
| 11 |
|
| 12 |
> > A more sensible approach would be for the ebuild to check which ebuild |
| 13 |
> > satisfies the virtual/editor dependency and set that. If the OP really |
| 14 |
> > cared about this "problem" he'd investigate providing such solutions |
| 15 |
> > instead of ranting about how Gentoo does not use his editor of choice |
| 16 |
> > by default. |
| 17 |
|
| 18 |
> The problem there would be if multiple editors provide virtual/editor |
| 19 |
> (such as on my system, which has both vim and ed installed). The ebuild |
| 20 |
> trying to automagically select what should be the default editor is a |
| 21 |
> bad idea, if not just horrible. |
| 22 |
|
| 23 |
You can't have it both ways. You want the program to default to an editor |
| 24 |
that is guaranteed to be there, at least at installation time, yet the |
| 25 |
only one that satisfies that is virtual/editor. It's only a default, it |
| 26 |
only has to be available the first time you run the program, whether |
| 27 |
it's your favourite editor or not. If you only want to use default |
| 28 |
configurations without making any changes to suit yourself, I suggest you |
| 29 |
may be better served by a distro that is a little browner. |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Neil Bothwick |
| 34 |
|
| 35 |
Gravity isn't easy, but it's the law. |
Archives