Re: Leo n00b on Mac OS X

2021-04-08 Thread tbp1...@gmail.com
I don't have a Mac, so I can't help much, but I can speak a bit about the 
*@path 
~* matter.  This does work on Linux.  When you wrote "does not expand", did 
you mean that the implied paths are not created when you save an "external" 
file?  If so, you can change this behavior by adding a node to your 
MyLeoSettings.leo file.  This node has to be a child of the @settings node, 
and have this headline:

@bool create_nonexistent_directories = True

Restart Leo after saving.  Then the following should happen.  Create a 
small subtree, for example:

- @path ~/aaa
   - @path bbb
  -@path ccc
  @clean test1.txt

After you save the outline, the file *test1.txt* should be there at 
*~/aaa/bbb/ccc/test1.txt*.

There are Mac users who seem to have good success using Leo, so it ought to 
workable for you.  A lot of them read these posts, so I expect you will get 
some help pretty soon.

Leo is a remarkably useful and adaptable piece of software.  But it can be 
hard to learn about all the things, like the *@bool* setting above, that 
make it really sing for you.  Just keep asking here, and read the Leo docs 
about settings, customization, and so on.
On Friday, April 9, 2021 at 12:07:00 AM UTC-4 kizz...@gmail.com wrote:

> Greetings,
>
> I discovered Leo a couple of days ago and think it might be valuable while 
> developing a new green field project (as well as maintaining some others). 
> We are a Mac-only shop and I have Leo up and running from the devel git 
> branch.
>
> With the caveat that I am still trying to get the hang of it, it seems to 
> be the case that Leo was not really targeted to OS X. There are areas some 
> areas where I cannot tell if I am doing something "wrong" or if there is a 
> "bug".
>
> Examples:
>
>
>- When I've had multiple .leo files open (tabs?) and tried to do 
>"insert child" nothing would happen in the visible outline, but would be 
>inserting children in one of the other non-visible outlines. Then after 
>closing the affected .leo file, save operations on the visible .leo file 
>would save the closed .leo file. Perhaps I do not understand how to 
> "Focus" 
>an outline for operations?
>- Most of the commands that specify the Ctrl- modifier in the docs are 
>mapped to "Command" correctly, but a lot of them don't actually work 
>(possible conflicts with OS X - Cmd-H for instance). Is there a Mac OS X 
>guide/cheat sheet available?
>- While setting up an outline with @path nodes, the '~' character does 
>not expand (as in quickstart.leo "Programming" node). Is there some plugin 
>I need for that to work?
>
> I look forward to mastering Leo for my needs as well as the VSCode-Leo 
> integration project (game changer?).
>
> Thanks,
> TK
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/1a20b782-ac34-45c7-9d92-325465c47079n%40googlegroups.com.


Leo n00b on Mac OS X

2021-04-08 Thread TEK42
Greetings,

I discovered Leo a couple of days ago and think it might be valuable while 
developing a new green field project (as well as maintaining some others). 
We are a Mac-only shop and I have Leo up and running from the devel git 
branch.

With the caveat that I am still trying to get the hang of it, it seems to 
be the case that Leo was not really targeted to OS X. There are areas some 
areas where I cannot tell if I am doing something "wrong" or if there is a 
"bug".

Examples:


   - When I've had multiple .leo files open (tabs?) and tried to do "insert 
   child" nothing would happen in the visible outline, but would be inserting 
   children in one of the other non-visible outlines. Then after closing the 
   affected .leo file, save operations on the visible .leo file would save the 
   closed .leo file. Perhaps I do not understand how to "Focus" an outline for 
   operations?
   - Most of the commands that specify the Ctrl- modifier in the docs are 
   mapped to "Command" correctly, but a lot of them don't actually work 
   (possible conflicts with OS X - Cmd-H for instance). Is there a Mac OS X 
   guide/cheat sheet available?
   - While setting up an outline with @path nodes, the '~' character does 
   not expand (as in quickstart.leo "Programming" node). Is there some plugin 
   I need for that to work?

I look forward to mastering Leo for my needs as well as the VSCode-Leo 
integration project (game changer?).

Thanks,
TK

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/5255af40-9a4e-4bac-bd7b-6fa2177a8109n%40googlegroups.com.


Re: [ctlug] M$ Joy

2021-04-08 Thread Steve Litt
David Wolfe said on Wed, 7 Apr 2021 11:11:48 -0500

>[ Lindsay Haisley writes: ]
>> I don’t have time to deal with word processor that’s not WYSIWYG.   
>
>Understandable from a get-work-done perspective. As you've pointed
>out, that's where most people live. Consider a traditional word
>processor UI like that in LibreOffice that uses one or more simple
>markup formats as its document representation. 

LibreOffice native format is a zipped group of six (IIRC) interrelated
XML files. It's not something like Asciidoc that's human readable and
easy to modify outside of a UI.

> I think Lyx is an old
>project that does this with TeX, but I don't have much experience with
>those. I remember not being impressed, but what if it could be made
>better?

LyX is a spectacular program **if** you're committed to it and if your
expected output is PDF and nothing else. It's a horrible way to write
things expected to be HTML or ePub. Also, LyX requires substantial LyX
expertise if you do any "off road driving". I've been writing books,
for sale to the public, in LyX, for the last 20 years, and it's worked
well for me.

>> IMHO, Libre office has improved over the years I’ve used it 
>> substantially more than most other project programs.  
>
>IMHO, LibreOffice has worked very hard matching MS Office 

As I posted in another email, I'm not a fan of LibreOffice. But I have
some other ideas...

First of all, if you're writing a book with very few styling
requirements, AsciiDoc just might be something that would satisfy
Lindsey. It's not WYSIWYG, but it's sub-one-second compilable to PDF,
so at any point you can see what's happening on the
layout/font/appearance front. Sort of like the "see in graphical
mode" feature of WordPerfect 5.1. Not requiring a mouse, Asciidoc's
*much* faster authoring than any word processor or something like LyX.
And if you need more formatting and features, you can upgrade to its
big brother, Asciidoctor.

I'm thinking that if the majority of your document is simple, but some
things, like your title page and copyright page, are complex with
exacting formatting needs, you can do each of those pages in Inkscape
(SVG), and link those into the document at the proper places. SVG
incorporates seamlessly into HTML, and if it doesn't work directly into
PDF, it can be auto-converted to encapsulated PDF or whatever before
the entire document is converted. This is what LyX does with graphics.

I'm also looking into something called Restructured Text and a program
called Sphinx that seems to be a front end for Restructured Text. It's
complicated and I don't think would be appropriate for Lindsey.

Another great text-only format you can do in any editor is Plain TeX
(***NOT*** LaTeX, which requires a Ph.D to do right). It has the
most of the advantages of Asciidoc but is much more versatile, although
it authors a little slower because you have to actually spell out style
names. Plain TeX is meant to compile to PDF, but a suitable subset of
Plain TeX could be used to simultaneously author valid-XML HTML5, and
therefore ePub. My biggest problem with Plain TeX is that using
anything other than TeX fonts is difficult, but I'm still looking into
it.

For about 8 years I've been trying to create a text-editor created
format called Stylz, which would do all this stuff the right way.
Unfortunately, it's a difficult programming project, and other than a
couple test documents, I haven't gotten it working. However, last night
at an online GoLUG meeting, I met a guy who created a similar product
for his own books, and I'll be looking into that.

Emacs Org-Mode is another possibility if you drive on that side of the
road, but I'm pretty sure that wouldn't be something Lindsey would be
interested --- it's a lot of work. 

There's also an outliner called Leo, which you can author entirely as
an outline with headlines that do or don't contain body text, and then
(I think) you can run a converter program, possibly one you'd need to
create yourself, to turn it into a ready made book, probably either PDF
or HTML/ePub. This isn't appropriate for Lindsey, because it's a huge
system with huge capabilities requiring a lot of knowledge: It's a
commitment. I'm copying the Leo list on this email.

I feel everybody's pain. As far as I know, there's not a single piece
of software out there that authors quickly and yet does consistent,
styles-based formatting and outputs to both PDF and HTML. But I'll keep
searching.

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/20210408085454.75dd454a%40mydesk.domain.cxm.