pacman -Ql eterm | grep bin or similar will tell you the executable name.
If experience serves correctly, it's Eterm.
On Mon, Apr 19, 2010 at 8:02 PM, Nathan Wayde wrote:
> On 20/04/10 03:56, Joe(theWordy)Philbrook wrote:
>
>>
>> Could be I'm missing something here... But shouldn't 'pacman -S e
On 20/04/10 03:56, Joe(theWordy)Philbrook wrote:
Could be I'm missing something here... But shouldn't 'pacman -S eterm'
put executable somewhere in the standard path??? This was done using a
root shell in a konsole terminal under E17 on my recently updated
Arch installation... I did search the w
Could be I'm missing something here... But shouldn't 'pacman -S eterm'
put executable somewhere in the standard path??? This was done using a
root shell in a konsole terminal under E17 on my recently updated
Arch installation... I did search the wiki for eterm just in case there
was something ab
On 20/04/10 00:36, José M. Prieto wrote:
2010/4/19 Arch Linux: Recent news updates: Daniel Griffiths
:
Daniel Griffiths wrote:
Users of vim/gvim should take note! The recently released update of vim/gvim
(7.2.411) introduces a few important changes. * We have moved vim/gvim to a
single PKGBUILD
2010/4/19 Arch Linux: Recent news updates: Daniel Griffiths
:
> Daniel Griffiths wrote:
>
> Users of vim/gvim should take note! The recently released update of vim/gvim
> (7.2.411) introduces a few important changes. * We have moved vim/gvim to a
> single PKGBUILD following the splitpkg format. * I
5 matches
Mail list logo
