How to install emacs on Kubuntu

[Leonard Chatagnier]

--- Grant Edwards <grante at visi.com> wrote:

> On 2008-08-11, Leonard Chatagnier
> <lenc5570 at sbcglobal.net> wrote:
> 
> > Well, it's not fully activated; you still have
> some
> > items(repositories) commented out so they wont be
> > checked.
> 
> OK, I checked everything except backports in the
> adept manager,
> and verified that it uncommented the corresponding
> entries in
> /etc/apt/sources.list
> 
Everything except backports, why?

> > Backports and Canonical are notable. Suggest you
> > uncomment all listings, then do "sudo aptitude
> update"
> 
> That hangs while attempting to connect.  After
> killing it, I
> tried "download updates" from the "Adept Manager". 
> It also
> hung for a while, and then "Adept Manager" crashed.
> 
> It appears that aptitude was ignoring the proxy
> setting I
> entered via the network manager. After setting the
> environment
> variable "http_proxy", it looks like aptitude is
> working from
> the command line.

Well, I can't help on proxies.  Have never used them;
don't know what they do or why one is needed and don't
think I want to know. Sorry about that.
> 
> So much for the GUI "manager" stuff...
> 
> I guess I'll go back to editing config files and
> running
> aptitude from the command line.
> 
I don't know what all the fuss is about command line
vs. GUI.  I've used both mostly aptitude from CLI to
install, purge or fix thigs rather than start up
snaptic or adept. I use adept updater for most updates
as it's conviently located in sys tray but have
actually used all to upgrade and dist-upgrade without
problems.  Just installed kde4.1 which is very buggy
and have some unresolved issues but dont think it's
related to the command line usage.

> > I'm assuming you are familiar with the command
> line
> > and use of apt-get/aptitude.
> 
> Yes.  I've been using Debian for many years (often
> on systems
> that don't even have X installed).  In the past I've
> been
> chastised for resorting to command line stuff and
> config file
> editing on Ubuntu systems and was told to use the
> provided GUI
> management stuff or else I'd "break my system".
> 
Well, I suppose you could break something by modifying
a config file incorrectly but I see where many
suggestions use a CLI but see where its said to use
gksu instead of sudo for GUI stuff. In KDE I've always
used "sudo nano" to edit everything and am not aware
of problems in doing it that way.
 
> That would be understandable advice if the GUI was
> sufficient
> to actually get a system up and running, but it
> doesn't seem to
> be.
> 
> Anyhow, the underlying cause of all this is that
> configuring a
> proxy in the network manager doesn't make
> apt/aptitude work.
> 
That could explain why you were having trouble that
you normally don't see, I guess. I'm dumb on that
issue. I expect you could teach me a lot about command
line use.  Glad to see you are making progress and
hope it continues.
>

Leonard Chatagnier
lenc5570 at sbcglobal.net