Fernando Meira wrote:
which I understand because it is trying to use *vi* and I don't have it.
If I'm not wrong, vi is not even in portage.
So, is there a way to work around this, maybe using another editor to
edit it?
It's probably hardcoded in the code.
Workaround:
$ sudo ln -s nano
I have changed the mouse input (from PS2 to USB) and solved that weird mouse behaviour.
The touchpad also works well. Strange that by PS2 gets so crazy.
Well, since things become more stable (at least until now), I been
learning how to work with e17. However, there's a small problem. When I
try
On Fri, 2005-08-05 at 17:42 +, Fernando Meira wrote:
which I understand because it is trying to use *vi* and I don't have
it. If I'm not wrong, vi is not even in portage.
So, is there a way to work around this, maybe using another editor to
edit it?
emerge vim and it should make vi
On 8/3/05, Justin Patrin [EMAIL PROTECTED] wrote:
I'm trying e17 as well after reading this ;-)
Great Justin :)
I suggest emerging edge before epsilon or you'll get compile errors.
I just finish compiling it and I got no problems (at least that I'm aware of)... so it also works with this sequence
Fernando Meira wrote:
Christoph, I can't find the screenshot I saw and made me think about
moving to E, but this one is also good and has the panel (right under
the IM app) I was talking about:
http://www.informatik.uni-oldenburg.de/~uriel/images/screen.jpg
In the browser window you can see
Fernando Meira wrote:
And in the E docs, there is this sentence:
Note that you should not mix -* and ~x86 ebuilds.
So is it enough that I just change everything to -* and all packages
will be upgraded, or will I need to unmerge every package before?
Just keyword all packages -* and update
Fernando Meira wrote:
Also found other scripts to compile directly from cvs, without using
portage. Can anyone tell me what the advantage of doing so?
I'd suggest using portage since it allows you to uninstall, query information
and doing other nice package managment stuff.
Christoph, is
Ok, thanks Christoph.
I'm just trying E17 for the first time now, and the first impression is good.
However, there a weird behaviour with the mouse. The mouse pointer
disappears very frequently, crashing from time to time one application.
xterm blew aways few minutes ago. In fact, this is the
Thanks anyway Luke!
This looks like a crazy mouse behaviour... suddenly jumps to another place and open the menu.
I think E17 never crashed (as I said before), but, in fact, what happen
(at least the last time) was that when the pointer jumped away, opened
the menu and (because I was trying to
On Thu, 2005-08-04 at 18:26 +, Fernando Meira wrote:
Thanks anyway Luke!
This looks like a crazy mouse behaviour... suddenly jumps to another
place and open the menu.
I think E17 never crashed (as I said before), but, in fact, what
happen (at least the last time) was that when the
Yes... that would maybe be good idea.
I'm using now the touchpad instead of the mouse and, until now, no weird behaviours!
Thanks.
FernandoOn 8/4/05, Luke Albers [EMAIL PROTECTED] wrote:
You should subscribe to the enlightenment-users@lists.sourceforge.net
mailing list and post this same message
On Wed, 2005-08-03 at 09:20 -0400, fire-eyes wrote:
On Wed, 2005-08-03 at 14:45 +0200, Fernando Meira wrote:
How stable is e17? The new stuff worth it? Any comments about this?
E17 is still beta or maybe even just alpha code. It is not stable by a
long shot, and I find it rather difficult
Luke Albers wrote:
I run this every day to recompile from CVS. Somtimes it compiles,
sometimes it doesnt, but I dont really care. I don't think it is
difficult to use at all, you will rarely need to change much from the
command line. The only thing that can be a bitch is making all the eapp
On Wed, 2005-08-03 at 17:59 +0200, Christoph Gysin wrote:
...
I'd suggest running this once:
...
and then the following each time you want to update:
emerge -v edb eet imlib2 imlib2_loaders evas ecore epeg epsilon embryo
edje esmart emotion etox ewl e engrave e_utils entrance evidence
Thank you all for answering :)
I'm getting the feeling that I should go for e17 after what I've been
seeing and reading!!! (though a few guys returned back to e16
afterwards).
Luke, you been using it for 3 months and never used e16. So, would you
said that I should start my experience with
I might be wrong, but isn't that a unnecessary step??
Even though you don't have anything else in package.keywords, once you
specify there the packages to unmask, you don't need to do it again
when you want to update E, right? Just running the 'emerge (...)' would
suffice...
FernandoOn 8/3/05,
On Wed, 2005-08-03 at 16:51 +, Fernando Meira wrote:
Thank you all for answering :)
I'm getting the feeling that I should go for e17 after what I've been
seeing and reading!!! (though a few guys returned back to e16
afterwards).
Luke, you been using it for 3 months and never used e16.
On Wed, 2005-08-03 at 16:56 +, Fernando Meira wrote:
I might be wrong, but isn't that a unnecessary step??
Even though you don't have anything else in package.keywords, once you
specify there the packages to unmask, you don't need to do it again
when you want to update E, right? Just
On Wed, 2005-08-03 at 18:55 +, Fernando Meira wrote:
On 8/3/05, Luke Albers [EMAIL PROTECTED] wrote:
I don't really understand the problem.
I use ~x86 for everything. What I pasted in my previous email
works
fine for me. I don't
On 8/3/05, Fernando Meira [EMAIL PROTECTED] wrote:
yes, i agree.
I just hope that's enough.
I'll emerge e17 now :D
I'll bring news.. soon..
I'm trying e17 as well after reading this ;-)
I suggest emerging edge before epsilon or you'll get compile errors.
On 8/3/05, Luke Albers
20 matches
Mail list logo
