If you make any changes or have any ideas, please share.
Email me with any suggeundostions you have
Installation Procedure
The easiest way to install aeditor and its dependencies is
through rpa-base, the port/pkg manager of the Ruby Production Archive.
1) Installing Fox Toolkit 1.0.X
\(WARNING\)
DON'T INSTALL FOX 1\.2\.X \!
On Gentoo, you can find it under /usr/portage/x11\-libs/fox
In Debian, you'll need to:
root$ apt\-get install libfox1\.0\-dev
FOX may be elsewhere on other platforms; you might be able to
find it in your system's package manager\.
2) Installing RPA
download and install RPA:
http://rubyforge.org/frs/?group_id=265&release_id=701
after installation, be sure to update rpa\-base:
root$ rpa update
root$ rpa install rpa\-base
3) Installing AEditor
root$ rpa install aeditor
AEditor is now installed, and you may start it by typing:
prompt$ aeditor
Installing the Dotfile
The syntax coloring rules are described in the dotfile; if it's missing,
no syntax coloring will take place.
I got some problems here after installing aeditor 1.5.
config,setup and installing were clean but right after start of
eaditor I got:
[aeditor-1.5/] :aeditor
did not found a configuration file
spawning editor in window mode.
/usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:286:in `initialize': uninitialized constant EditorWidget::FXMenubar (NameError)
from /usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:1523:in `new'
from /usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:1523:in `onSpawnEditor'
from /usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:1519:in `loop'
from /usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:1519:in `onSpawnEditor'
from /usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:1577:in `run'
from /usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:1577:in `run'
from /usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:1571:in `initialize'
from /usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:1571:in `new'
from /usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:1571:in `run'
from /usr/lib/ruby/site_ruby/1.8/aeditor/main.rb:6:in `launch_editor'
from /usr/lib/ruby/site_ruby/1.8/aeditor/cli.rb:35:in `parse'
from /usr/lib/ruby/site_ruby/1.8/aeditor/cli.rb:83:in `parse'
from /usr/lib/ruby/site_ruby/1.8/aeditor/main.rb:26
from /usr/bin/aeditor:2:in `require'
from /usr/bin/aeditor:2
I _thought_ I have installed everything needed, but...
Thank you very much for any help !
Kind regards,
Meino
···
From: Simon Strandgaard <neoneye@adslhome.dk>
Subject: [ANN] aeditor 1.5
Date: Fri, 13 Aug 2004 07:36:33 +0900
AEditor is an übercool programmer's editor, written entirely in Ruby
and very easy to extend with your own customizations.
If you make any changes or have any ideas, please share.
Email me with any suggeundostions you have
Installation Procedure
The easiest way to install aeditor and its dependencies is
through rpa-base, the port/pkg manager of the Ruby Production Archive.
1) Installing Fox Toolkit 1.0.X
\(WARNING\)
DON'T INSTALL FOX 1\.2\.X \!
On Gentoo, you can find it under /usr/portage/x11\-libs/fox
In Debian, you'll need to:
root$ apt\-get install libfox1\.0\-dev
FOX may be elsewhere on other platforms; you might be able to
find it in your system's package manager\.
2) Installing RPA
download and install RPA:
http://rubyforge.org/frs/?group_id=265&release_id=701
after installation, be sure to update rpa\-base:
root$ rpa update
root$ rpa install rpa\-base
3) Installing AEditor
root$ rpa install aeditor
AEditor is now installed, and you may start it by typing:
prompt$ aeditor
Installing the Dotfile
The syntax coloring rules are described in the dotfile; if it's missing,
no syntax coloring will take place.
I got some problems here after installing aeditor 1.5.
config,setup and installing were clean but right after start of
eaditor I got:
[aeditor-1.5/] :aeditor
did not found a configuration file
spawning editor in window mode.
/usr/lib/ruby/site_ruby/1.8/aeditor/viewfox.rb:286:in `initialize':
uninitialized constant EditorWidget::FXMenubar (NameError) from
[snip backtrace]
I _thought_ I have installed everything needed, but...
Hmm.. I suspect you maybe have a different version of fox.. did you install
Fox 1.2.x ?
AEditor 1.5 doesn't work with the Fox 1.2.x (but its on my todo).
Please chect the version numbers of aeditors dependencies.
no colors.. hmm.. syntax coloring is only enabled through the
configuration file (.aeditor); if its missing then no colors.
Thats usually the reason.. (it has happened quite a few times
<copy from announcement>
The syntax coloring rules are described in the dotfile; if it's missing,
no syntax coloring will take place.
That most likely is a FOX 1.2.x library, when I was
hacking at the code to work nice with FOX 1.0.x, that
was the error I did get. Something is wrong with
FXMenuBar
> I got some problems here after installing aeditor
1.5.
>
> config,setup and installing were clean but right
after start of
> eaditor I got:
>
> [aeditor-1.5/] :aeditor
> did not found a configuration file
> spawning editor in window mode.
>
--- Simon Strandgaard <neoneye@adslhome.dk> wrote:
On Sunday 15 August 2004 11:08, Meino Christian > Cramer wrote:
`initialize':
> uninitialized constant EditorWidget::FXMenubar
(NameError) from
[snip backtrace]
>
> I _thought_ I have installed everything needed,
but...
Hmm.. I suspect you maybe have a different version
of fox.. did you install
Fox 1.2.x ?
AEditor 1.5 doesn't work with the Fox 1.2.x (but
its on my todo).
Please chect the version numbers of aeditors
dependencies.
Simon Strandgaard wrote:
> > Dunnit. I'm not talking about installing the highlighting. I'm talking
> > about after it works. All the colors are dark, and the background
> > black.
>
> Very odd.. hmm
>
> Can you change to 'turbo' theme via the View pulldown menu?
Okay. Turbo and Gvim themes don't suck.
Great.. im happy it works.. admitted the default theme sux..
Its just me when I make changes to the syntax coloring code.. then
I make changes to the default theme.. this way it has become ugly.
Maybe I should find a nice default theme?
If you manage to make a nice theme which you think are
suitable.. then please mail me
When I use View->Customize Theme, all the colors are drab and dark.
It's like you were CGA with the bright bit always off. (There I go showing
my age again...)
Hmm.. can you upload another screenshot where you capture
both the Customize Theme dialogbox and the mainwindow at the same time.
This sounds also odd.. The Customize Theme is suppose to reflect
the currently chosen theme. Dark colors shouldn't be there.
> However, I can't think now, because "Jah's Music" has just started
> [...] Excellent programming music, everyone!
That sounds somewhat contradictual.
De riddims of de sacred party music gwine 'spire I-an-I de "mental state
called flow", Jah!
(With the herbal assistance of Yuban coffee mixed with Hershey's Special
Dark Chocolate. I wouldn't want y'all to think I was being a prude about
it...
