Bug#296297: ash: menu entry for ash
On Mon, Feb 28, 2005 at 07:08:55PM +0100, Bill Allombert wrote: On Mon, Feb 28, 2005 at 05:05:09PM +, Gerrit Pape wrote: do people really choose ash from a menu to have it open an interactive shell in a new window? I wouldn't mind if you simply remove the item from the menu package, I personally don't see a need for it. How did it get there, has it been requested by users? I will hazard the guess that this file was added to one of the first menu package release circa 1997. However, the Debian menu subpolicy list a dedicated menu section for shells (Apps/Shells) and it is more consistent to have all shells listed there. (why providing a shell if it is not supposed to be used ?) dash primarily is meant to run non-interactively, and to be used as a standard /bin/sh interpreter for shell scripts. I think I'll add the menu file to the dash package nevertheless (today's ash package only provides a symlink /bin/ash - dash), so it should be fine if you remove /usr/share/menu/default/ash from the menu package. Regards, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296297: ash: menu entry for ash
On Tue, Mar 01, 2005 at 09:05:36PM +, Gerrit Pape wrote: On Mon, Feb 28, 2005 at 07:08:55PM +0100, Bill Allombert wrote: On Mon, Feb 28, 2005 at 05:05:09PM +, Gerrit Pape wrote: do people really choose ash from a menu to have it open an interactive shell in a new window? I wouldn't mind if you simply remove the item from the menu package, I personally don't see a need for it. How did it get there, has it been requested by users? I will hazard the guess that this file was added to one of the first menu package release circa 1997. However, the Debian menu subpolicy list a dedicated menu section for shells (Apps/Shells) and it is more consistent to have all shells listed there. (why providing a shell if it is not supposed to be used ?) dash primarily is meant to run non-interactively, and to be used as a standard /bin/sh interpreter for shell scripts. I think I'll add the menu file to the dash package nevertheless (today's ash package only provides a symlink /bin/ash - dash), so it should be fine if you remove /usr/share/menu/default/ash from the menu package. Ah, thanks. I though dash was not interactive but ash was (and that was the point of having both). In fact I though ash was the current *BSD version and dash was the Debian version. So why did Herbert renamed ash to dash ? Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296297: ash: menu entry for ash
On Tue, Mar 01, 2005 at 11:05:11PM +0100, Bill Allombert wrote: On Tue, Mar 01, 2005 at 09:05:36PM +, Gerrit Pape wrote: dash primarily is meant to run non-interactively, and to be used as a standard /bin/sh interpreter for shell scripts. I think I'll add the menu file to the dash package nevertheless (today's ash package only provides a symlink /bin/ash - dash), so it should be fine if you remove /usr/share/menu/default/ash from the menu package. Ah, thanks. I though dash was not interactive but ash was (and that was the point of having both). In fact I though ash was the current *BSD version and dash was the Debian version. So why did Herbert renamed ash to dash ? I'm not sure, but I think to point out that's a code fork. Changing the name in such a case is a good thing in my opinion, to avoid confusion. dash can be used interactively of course, but doesn't include convenient features like readline and history support, currently. Regards, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296297: ash: menu entry for ash
On Tue, Mar 01, 2005 at 10:58:49PM +, Gerrit Pape wrote: On Tue, Mar 01, 2005 at 11:05:11PM +0100, Bill Allombert wrote: On Tue, Mar 01, 2005 at 09:05:36PM +, Gerrit Pape wrote: dash primarily is meant to run non-interactively, and to be used as a standard /bin/sh interpreter for shell scripts. I think I'll add the menu file to the dash package nevertheless (today's ash package only provides a symlink /bin/ash - dash), so it should be fine if you remove /usr/share/menu/default/ash from the menu package. Ah, thanks. I though dash was not interactive but ash was (and that was the point of having both). In fact I though ash was the current *BSD version and dash was the Debian version. So why did Herbert renamed ash to dash ? I'm not sure, but I think to point out that's a code fork. Changing the name in such a case is a good thing in my opinion, to avoid confusion. Ah I see, so ash is a dummy package for smooth upgrade ? I was completly off mark then. dash can be used interactively of course, but doesn't include convenient features like readline and history support, currently. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296297: ash: menu entry for ash
Hi Bill, On Mon, Feb 21, 2005 at 05:17:43PM +0100, Bill Allombert wrote: For legacy reason, the menu package include a menu entry for ash. This practice is deprecated, it is better to move the menu netry to the ash packages. Such menu entry is for the Apps/Shells section of the menu Here it is: ?package(ash):needs=text section=Apps/Shells title=Ash command=/bin/ash -i So could you add such menu entry to the ash package so that I can remove it frome menu ? do people really choose ash from a menu to have it open an interactive shell in a new window? I wouldn't mind if you simply remove the item from the menu package, I personally don't see a need for it. How did it get there, has it been requested by users? Thanks, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296297: ash: menu entry for ash
On Mon, Feb 28, 2005 at 05:05:09PM +, Gerrit Pape wrote: Hi Bill, On Mon, Feb 21, 2005 at 05:17:43PM +0100, Bill Allombert wrote: ?package(ash):needs=text section=Apps/Shells title=Ash command=/bin/ash -i So could you add such menu entry to the ash package so that I can remove it frome menu ? do people really choose ash from a menu to have it open an interactive shell in a new window? I wouldn't mind if you simply remove the item from the menu package, I personally don't see a need for it. How did it get there, has it been requested by users? I will hazard the guess that this file was added to one of the first menu package release circa 1997. However, the Debian menu subpolicy list a dedicated menu section for shells (Apps/Shells) and it is more consistent to have all shells listed there. (why providing a shell if it is not supposed to be used ?) Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296297: ash: menu entry for ash
Package: ash Version: 0.5.2-1 Severity: minor Hello Gerrit, For legacy reason, the menu package include a menu entry for ash. This practice is deprecated, it is better to move the menu netry to the ash packages. Such menu entry is for the Apps/Shells section of the menu Here it is: ?package(ash):needs=text section=Apps/Shells title=Ash command=/bin/ash -i So could you add such menu entry to the ash package so that I can remove it frome menu ? Thanks in advance, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
