Re: a little lilybuntu help

[Trevor Daniels]

Jonathan Kulp wrote Sunday, December 06, 2009 1:20 PM
>

> On Sun, Dec 6, 2009 at 6:41 AM, Trevor Daniels 
> <address@hidden>wrote:
> > I'm hardly an expert, having installed ubuntu myself
> > only a few days ago, but the default editor in ubuntu
> > from Jonathan's .iso seems to be gedit.  This certainly
> > supports utf8 - it's the default.  Text wrapping can be
> > set, but this simply wraps text on the screen, determined
> > by the window width, but it does not wrap text in the file
> > itself.
> >
> > (As an aside, I tried using gedit as the git default editor.
> > It didn't work out.  gedit was called fine, but it refused
> > to save the amended file that git provided saying it
> > couldn't find the file name.  I've gone back to using nano
> > for git edits.)
>
> As a graphical editor I prefer Geany, but I can't figure how to 
> make it wrap
> with proper line endings either. What I like about it for 
> documentation work
> is that there's a menu item to remove trailing spaces on the file, 
> and also
> one that shows line endings and stuff.  It doesn't have texinfo 
> syntax
> coloring by default though. :(
>
> For the git edits, nano is probably the easiest to deal with. Vim 
> and Emacs
> both have steeper learning curves and are probably overkill for 
> git commit
> messages. I'm sorry to hear that gedit didn't work out for this. 
> Have you
> tried using git-gui for this? If it's not installed already try 
> "sudo
> apt-get install git-gui" and after it's installed, type "git gui" 
> from the
> top directory. I imagine it's similar to the interface you used on 
> Windows.

Yes, I did that some time ago, as I prefer git gui
to the command line interface to git for most operations,
especially commit messages.  It is indeed identical to
the windows version.

However, it's not relevant to the interactive editor
that pops up with, for example, git rebase -i ...  Nano
is actually fine for that, since all you have to do
is change a couple of lines, as long as you know that the
defaults are fine when saving/editing - that's what threw
me the first time it popped up.

> Jon

Trevor