Hello,

I came to Leo because it is the only outliner for Linux that supports
cloning that doesn't require an internet connection.

I am struggling to implement it into my workflow though, simply because I
do not have time to figure out the simplest things. (full time university
student) Right now I simply do not have the 200 minutes available to figure
this out. Yet I can see that if I took the time to do my own setup it would
save me far more time in the future. Leo would be a wonderful platform for
writing anything, but especially for fiction. If there was a tutorial on
setting up Leo to do the following, I know there would be immediate
interest from people who write on Linux as there simply is not an outliner
that meets the needs of the average writer.

I need basic text formatting at the standard hot key level. ie. Ctrl-B for
bold, Ctrl-I for italic etc. while in the edit window. I know this can be
done, I almost had it working once but then got busy and by the time I came
back it had escaped me how I had done it. I don't need buttons, I don't
need WSIWYG, RST markup works fine as it gives me lots of output options. I
just need the ability to put my head down and write, using the shortcuts
that are baked into my fingertips at this point, and not having to relearn
those keys. Support for standard word-processing keys are important for
writers. :-)

I think that by creating tutorials that address the basics for different
groups of users who are not programmers, Leo could be an extremely popular
program. I would be willing to contribute to such an effort for writers if
I can get a workflow setup that makes sense for me. My current editor of
choice is Scrivener for Windows run using Crossover. No cloning. :-(

Leo is far too complex for the average person who simply wants to
accomplish a task. Simplifying things for specific classes of users would
open Leo up to many more people who share those requirements and may be
interested in learning the rest of the power of Leo as their use of it
increases. Give people a foot in the door and they will figure out how to
open it the rest of the way as needed.

Chris




On Mon, Sep 30, 2013 at 8:51 AM, Miles Fidelman
<[email protected]>wrote:

> [email protected] wrote:
>
>> On Monday, 30 September 2013 17:26:37 UTC+2, Miles Fidelman wrote:
>>
>>     I'm surprised nobody has mentioned this yet:  Leo has pretty much
>>     written off Mac users, and close to written off large chunks of
>>     Linux users.
>>
>>     Sure, you CAN install and get it to work on Macs and Debian/Ubuntu
>>     (and
>>     presumably other linux varieties).  But... it's pretty hard to
>>     justify
>>     the time and effort, just to try Leo the first time.
>>
>>     Point and click for windows, and there seems to be a port for BSD,
>>     but
>>     while there's mention of a package for Debian and Ubuntu I can't
>>     seem to
>>     find it in the respective package repos.  No Mac package for Fink or
>>     MacPorts - just some instructions on how to use Homebrew (and does
>>     one
>>     really want to use a Ruby based installer to install something
>>     written
>>     in Python?).
>>
>>     Somehow, one gets just a little squirrely contemplating a Python
>>     based
>>     IDE that seems to have been targeted at a Windows environment. That
>>     alone raises some red flags.
>>
>>
>> More needs to be done in the marketing department.
>>
>
> In that regard, Leo is barely mentioned on WikiPedia - it has a simple
> descriptive page, but on the list of text editors it's listed, but there's
> no information about o/s support or features.
>
> For marketing, packaging, features, documentation, tutorials,
> extensions,... - do a side by side comparison of Vim and Leo - and the
> answer(s) to "why leo isn't more popular" leap out at you.
>
>
> Miles Fidelman
>
> --
> In theory, there is no difference between theory and practice.
> In practice, there is.   .... Yogi Berra
>
> --
> You received this message because you are subscribed to the Google Groups
> "leo-editor" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to 
> leo-editor+unsubscribe@**googlegroups.com<leo-editor%[email protected]>
> .
> To post to this group, send email to [email protected].
> Visit this group at 
> http://groups.google.com/**group/leo-editor<http://groups.google.com/group/leo-editor>
> .
> For more options, visit 
> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to