On Sat, Feb 14, 2009 at 10:34 PM, Bill Baxter <[email protected]> wrote: > > On Sat, Feb 14, 2009 at 9:24 AM, Christopher Barker > <[email protected]> wrote: >> It seems you can't quite use leo as "just a text editor" out of the box. >> >> Still on the fence here..... > > Just out of curiosity -- Edward and any other Leo users out there. Do > you actually use Leo for small editing tasks like Christopher > described? Say you need to edit your bazaar.conf file, a simple .ini > file with two lines in it. Is Leo the tool you reach for in that > case?
I don't 'reach for' Leo, I 'work from' Leo I open a Leo file which organizes my stuff ~/work/project/start.leo (the Leo standard is a file named ~/.leo/workbook.leo) bazaar.conf is available as @auto ~/.bazaar/bazaar.conf which is a child of a top level node named 'configure' which aggregates configuration files:: configure @auto ~/bazaar/.bazaar.conf @auto conf.py @auto ~/.bashrc @auto ~/.bzrignore ... editing the contents of an @auto node and saving the .leo file changes the file on the filesystem. > Or do you keep another more basic editor on hand for those > things. I'll sometimes double click the @auto node and edit in Vim, for a small file I'll edit in Leo, but to do any extensive search/replace stuff I prefer Vim. Thanks, Kent > Emacs is generally my first choice, even for tiny edits like > that. > > --bb >
