Re: my 2 cents to embedding Leo into other editor or vice versa

[Matt Wilkie]

> After a while I thought that easiest way to connect the two is 
> implementing some kind of special file system. In this (let's call it 
> LeoFS), filenames are gnxes and file content is the body or maybe (headline 
> + '\n' + body). All these editors have some kind of tree representation of 
> the file system which can be enhanced to draw Leo icons and headlines 
> instead of filenames.
>
 [...]

> I am amazed how no one has implemented such feature in any other editor 
> yet. Due to the lack of time I had to abandon this idea but it still burns 
> in the back of my head waiting for a better time to be realized.
>

Here's one my smouldering embers: A long time ago, before I ever considered 
learning how to script or program, I was intensely involved and enthused 
with Wiki's in general and TWiki in particular. One of the problems 
inherent in text-based wiki's, 99% of them, is how to reference and store 
media such as pictures, sound, videos, pdfs,  For the most part all of 
the wiki engines solve the reference part more or less succinctly and 
sometimes elegantly. Unfortunately the accessories storage part is shoved 
to the side -- usually one big heap with some kind of human illegible 
machine generated index. (This isn't unique to wiki's. This same 'media 
ghetto' solution is used by almost every content management system I've had 
occasion to use.) 

 

My conceptual solution to this was/is "What If Topics Were Folders?", 
topics being the twiki version of Nodes. Basically: every topic is a 
container, within the container if the default file exists, display that 
using the filetype's default rendering mechanism (think web servers and 
index.html). Media files could be "attached" simply by storing in the same 
container and then referenced with a link from the default file. Any topic 
can contain other topics, and thus media files, recursively. A text file 
would be the global default rendering file, but that could be changed for a 
local topic/branch to use video or audio or graph instead.

 

All this is a really long way of saying: I agree with you. Filesystems are 
a smashing great idea. Nodes are a smashing great idea. Putting them 
together would be awesome.

 

 matt

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rethinking Leo's distribution process

[Matt Wilkie]

>
> I can't find assoc.exe in the source code for Leo. Where is it? What does 
> it do? 
>

I do find in the *scripts* folder within the Leo source code files 
> *register-leo.leox* and *unregister-leo.leox *- these handle Windows 
> Registry entries for using *launchLeo.py* for a simple one of the (many!) 
> scenarios supported by Microsoft. Are these scripts deprecated, or are they 
> in active use?
>

`assoc.exe` ships with Windows. It's usually used in concert with 
`ftype.exe`. See 
http://leoeditor.com/installing.html#creating-windows-file-associations 
"Method 2" for example usage. The (un)register leo scripts basically just 
execute those commands, plus some logic for elevated privileges, wrapped in 
Leo for ease of use.

As for active use, I don't know if anyone besides myself have used them. I 
know they're broken right now, a unicode error (#779 
), but once that is 
fixed I believe them to be still viable.

matt

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: How did I came across Leo?

[Matt Wilkie]

>
> ​@root and Leo's tangle and untangle commands will remain "forever".  They 
> are, on purpose, no longer documented, [...]
>

I would hope they are documented *somewhere* though? Perhaps within the 
code if no place else. I imagine a future self shooting myself in the foot 
while I spin this unknown thing this way and that wondering what it does. 
;-)

matt

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Should daily snapshots be based on master, devel or both?

[Matt Wilkie]

>
> I don't know that snapshots are needed at all
>> ​.
>>
>
> ​I'm not sure either, but I think some people do/did use them.​
>   
>

Maybe Terry has download stats?

 

> Github allows downloading at will, ex: 
>>
>> wget https://github.com/leo-editor/leo-editor/archive/devel.zip
>>
>> pip install https://github.com/leo-editor/leo-editor/archive/devel.zip
>>
>> Same for any tag: https://github.com/leo-editor/leo-editor/tags
>>
>
> ​Cool. ​We can assume pip is installed, but not wget (at least on Windows).
>
> What does devel.zip contain? A very quick google doesn't tell me.
>

'devel' is just the name of the branch or tag or commit hash. It could just 
as easily be `master.zip 
`, `
fix-empty-description.zip 
`, 
or `bd5ba40f76220325e9d4dc25c6afbc2841083cb9.zip 

`

matt

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to push or pull from devel

[Terry Brown]

On Sun, 4 Mar 2018 14:36:04 -0800 (PST)
vitalije  wrote:

> On Sunday, March 4, 2018 at 11:30:55 PM UTC+1, vitalije wrote:
> >
> > It seems according to your log that the conflict is caused 
> > by leo/core/commit_timestamp.json
> >
> >
> > This made me think about. It is not first time that I had troubles
> > with   
> this file. Because it is automatically changed every time commit is 
> executed, quite often it prevents merge. Perhaps with the new scheme
> of working on devel branch and just occasionally merging it to
> master, it may be good to skip updates to this file when in devel
> branch. That would reduce probability of code conflicts.
> 
> Vitalije

Hi Vitalije,

I forget whether the rather protracted discussions about
commit_timestamp.json were before or after your joining us, but the
goal was to have a unique identifier for a commit, without requiring a
user to use git.  I don't think it's reasonable to require non-coders
to use git to get current Leo, e.g. for Leo with an attempted fix for a
bug the user might have reported, where precise commit ID is important.
I do kind of expect them to be able to use zip, as in
https://github.com/leo-editor/leo-editor/archive/devel.zip
but that doesn't include a git commit hash.  So that's what the Leo
build timestamp solution was supposed to solve.

I usually fix the conflict it creates with

  git checkout --theirs leo/core/commit_timestamp.json

but I *think* you can also add

leo/core/commit_timestamp.json merge=ours

to .gitattributes, but maybe you also need to do

git config --global merge.ours.driver true

for that to work, not clear to me.

Cheers -Terry

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to push or pull from devel

[vitalije]

On Sunday, March 4, 2018 at 11:30:55 PM UTC+1, vitalije wrote:
>
> It seems according to your log that the conflict is caused 
> by leo/core/commit_timestamp.json
>
>
> This made me think about. It is not first time that I had troubles with 
this file. Because it is automatically changed every time commit is 
executed, quite often it prevents merge. Perhaps with the new scheme of 
working on devel branch and just occasionally merging it to master, it may 
be good to skip updates to this file when in devel branch. That would 
reduce probability of code conflicts.

Vitalije

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to push or pull from devel

[Edward K. Ream]

On Sunday, March 4, 2018 at 4:30:55 PM UTC-6, vitalije wrote:
>
> It seems according to your log that the conflict is caused 
> by leo/core/commit_timestamp.json
>
> Try
> git checkout --force leo/core/commit_timestamp.json
> # then
> git pull devel
>
> to discard your changes to this file. It will be changed automatically 
> when you commit next time.
>

Didn't work.  Actually, I have already successfully pushed everything to 
devel.  I'll just do a clean git clone.

Edward 

>
> Vitalije
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to push or pull from devel

[vitalije]

It seems according to your log that the conflict is caused 
by leo/core/commit_timestamp.json

Try
git checkout --force leo/core/commit_timestamp.json
# then
git pull devel

to discard your changes to this file. It will be changed automatically when 
you commit next time.

Vitalije

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to push or pull from devel

[Edward K. Ream]

On Sunday, March 4, 2018 at 2:07:26 PM UTC-6, Jacob MacDonald wrote:

I'm on devel, not detached.

What's the error message?
>

Here's what I did:

>git push

 ! [rejected]devel -> devel (non-fast-forward)
error: failed to push some refs to 
'https://github.com/leo-editor/leo-editor'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.

> git pull

Already up-to-date.

> git pull --rebase

First, rewinding head to replay your work on top of it...
Applying: Added Matt's instructions for creating a Python wheel for Leo
Using index info to reconstruct a base tree...
M   leo/core/commit_timestamp.json
Falling back to patching base and 3-way merge...
Auto-merging leo/core/commit_timestamp.json
CONFLICT (content): Merge conflict in leo/core/commit_timestamp.json
error: Failed to merge in the changes.
Patch failed at 0001 Added Matt's instructions for creating a Python wheel 
for Leo
The copy of the patch that failed is found in: .git/rebase-apply/patch

When you have resolved this problem, run "git rebase --continue".
If you prefer to skip this patch, run "git rebase --skip" instead.
To check out the original branch and stop rebasing, run "git rebase --abort"
.

> git status

rebase in progress; onto 6c2eef2
You are currently rebasing branch 'devel' on '6c2eef2'.
  (fix conflicts and then run "git rebase --continue")
  (use "git rebase --skip" to skip this patch)
  (use "git rebase --abort" to check out the original branch)

Changes to be committed:
  (use "git reset HEAD ..." to unstage)

modified:   leo/dist/leoDist.leo

Unmerged paths:
  (use "git reset HEAD ..." to unstage)
  (use "git add ..." to mark resolution)

both modified:   leo/core/commit_timestamp.json

And now I'm stuck.  Nothing works from here.

I think I'll back up recently changed files and do a clean clone.

Edward

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to push or pull from devel

[Terry Brown]

On Sun, 4 Mar 2018 11:00:37 -0800 (PST)
"Edward K. Ream"  wrote:

> git push and git pull --rebase both fail. Anyone have any suggestions?
> 
> Edward

You're head's not detached is it?  :-)

I was on a "detached head" just now, from using git bisect, when I tried
to test, but after checking out first master and then devel, I was able
to pull (both) without any trouble.

Cheers -Terry

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: leovue meets leo4sqlite

[Joe Orr]

Fixed the bookmarks in subtrees. This links work now:

https://kaleguy.github.io/leo-examples/leo4sqlite/#/t/5-26/
https://kaleguy.github.io/leo-examples/leo4sqlite/#/t/4-23/

Joe

On Sunday, March 4, 2018 at 11:28:55 AM UTC-5, Joe Orr wrote:
>
> About the commands not displaying on separate lines, this is because I'm 
> using a markdown module with a few hacks. With markdown you need to either 
> put a blanks space between lines or make bullets etc.
>
> See the example here: 
> https://kaleguy.github.io/leo-examples/leo4sqlite/#/t/4
>
> To get a bullet, you just need to put a * at start of line.
>
> The code for transforming the docstrings is hacks + markdown module, so 
> I'm guessing there will be some refinements necessary as further examples 
> get posted, but I don't think it will be easy to get around having to 
> signal a break the way markdown does.
>
> Joe
>
>
>
> On Sunday, March 4, 2018 at 2:57:05 AM UTC-5, tscv11 wrote:
>>
>> *UPDATE: *The syntax highlighting of the docstring in node 'Sqlite3' now 
>> displays correctly, but the commands near the bottom are supposed to appear 
>> on their own lines (I'm sure it's a problem with my rusty reST, not 
>> Leovue). I've also added the beginnings of a Kanban, and may even do a 
>> Mermaid chart... thanks to Joe Orr, all of this and more is possible! :) 
>>
>> tscv11
>>
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to push or pull from devel

[Jacob MacDonald]

What's the error message?

On Sun, Mar 4, 2018, 13:00 Edward K. Ream  wrote:

> git push and git pull --rebase both fail. Anyone have any suggestions?
>
> Edward
>
> --
> 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 post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Unable to push or pull from devel

[Edward K. Ream]

git push and git pull --rebase both fail. Anyone have any suggestions?

Edward

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: leovue meets leo4sqlite

[Joe Orr]

About the commands not displaying on separate lines, this is because I'm 
using a markdown module with a few hacks. With markdown you need to either 
put a blanks space between lines or make bullets etc.

See the example here: 
https://kaleguy.github.io/leo-examples/leo4sqlite/#/t/4

To get a bullet, you just need to put a * at start of line.

The code for transforming the docstrings is hacks + markdown module, so I'm 
guessing there will be some refinements necessary as further examples get 
posted, but I don't think it will be easy to get around having to signal a 
break the way markdown does.

Joe



On Sunday, March 4, 2018 at 2:57:05 AM UTC-5, tscv11 wrote:
>
> *UPDATE: *The syntax highlighting of the docstring in node 'Sqlite3' now 
> displays correctly, but the commands near the bottom are supposed to appear 
> on their own lines (I'm sure it's a problem with my rusty reST, not 
> Leovue). I've also added the beginnings of a Kanban, and may even do a 
> Mermaid chart... thanks to Joe Orr, all of this and more is possible! :) 
>
> tscv11
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: The first, urgent task: show people what Leo already has

[Edward K. Ream]

On Saturday, March 3, 2018 at 6:11:44 PM UTC-6, Edward K. Ream wrote:

> I have just spent all afternoon wrestling with themes. 

All is now well.  I have something that looks great on both Windows and 
Ubuntu.  Except for a few tweaks the result is just as before.  

This comment 
 
in #764  contains the 
new, much simpler, @theme node. Read the comment for more details.

I plan to use this theme on both Windows and Ubuntu.  I'll be updating 
Leo's screen shot as soon as I tweak it some more.

Edward

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: I love Leo, but... Scrivener and Org-Mode

[Israel Hands]

Thanks Edward a simple route to Latex would be brilliant. 

Leo does indeed open org mode files. And it takes each entry in a .org file 
and turns it into a node. 
With some help from Terry I've started writing a script that sorts the 
nodes from the org-mode file by date stamp, which org uses to produce the 
agenda.  
In the source file the org agenda items are not chronological the Agenda 
view imposes the chronology.  There is a calendar framework into which the 
agenda items are filed. The calendar does not 'know' what day it is in real 
time. You have to manually sync it - which doesn't seem to be a problem for 
users. And there are commands for how much of a calendar to produce - this 
week, this month, this year. 

I suppose having sorted the agenda items in Leo and having a calendar 
framework, node per day maybe? Then we just copy the child nodes to the 
relevant day for each item.  And then some sort of manual sync process that 
takes the view to the node for 'Today'  
When I write that down it doesn't sound too complicated. I have the sorting 
bit mostly working so maybe I should have a go at the next bit. However I'm 
very conscious of how thin the ice of my competence is!

Thinking about it there must be some real time checking going on because 
org-mode is able to fire off an OS based reminder when a scheduled or 
deadlined item becomes due. 

Enough thinking out loud,  Ta like. 

IH




On Saturday, 3 March 2018 13:16:33 UTC, Edward K. Ream wrote:
>
> On Sat, Mar 3, 2018 at 6:50 AM, Israel Hands  > wrote:
>
> ​> ​
> Disclaimer
>
> ​No need for that.
>
> ​>
> ​ ​
> Scrivener
> ​.. ​
> has a relatively simple 'compile' mode to Latex.
>
> ​#774 Convert Leo trees to LaTex as in Scrivener 
>  is a new 
> enhancement request. 
>
> Googling "scrivener convert to LaTeX" yields this page 
> . 
> It doesn't look to difficult to translate this approach into Leo. I've 
> given it a 5.7.1 milestone, which means it will happen this year.
>
> ​> ​
> Seeing my Org Mode Agenda in Leo would be lovely
> ​.
>
> Leo supposedly can read .org files.  Have you tried doing so? 
>
> > Having that agenda fire reminders from Leo would be even better.
>
> #775: Support org mode agendas in Leo 
>  is another 
> enhancement request.
>
> This has a 5.8 milestone, which is no guarantee that it will be done soon.
>
> ​Edward​
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: I love Leo, but... Scrivener and Org-Mode

[Israel Hands]

Thanks Rob,

I agree with you about the limitations of Scrivener to Latex - which are 
due to the fact that the process is actually Scrivener MultiMarkDown then 
to Latex. This is great because MultiMarkDown is very clean - very 
uncluttered compared with the Latex file full of mark up commands. However 
it is limiting because you can't just drop in a Latex command in the MMD 
file and get it out the other end. I think there is a way but it seemed 
very cumbersome to me. This also means there is confusion about what is the 
master file - is it the Markdown file in Scrivener or the compiled Latex 
file on the OS file system.  The worst thing is the temptation to edit the 
Latex file directly as now your Scrivener master is out of sync, not good. 
But always returning to Scrivener is  slower process.  
Your work flow sounds good - I can imagine abbreviations would be a big 
help and it would be nice to standardise them early on!
Emacs can drive the Latex engine in the background and then sync with a pdf 
viewer - I'm sure Leo could do this just as well, if not better. 

IH


On Saturday, 3 March 2018 22:51:06 UTC, Largo84 wrote:
>
> Wow, reading Israel's post made me me think I wrote it (except the 
> org-mode part). Probably 80+% of my work in Leo is writing content w/ LaTEX 
> output. Most of the rest is variations of markdown and RST. I tried moving 
> my work to Scrivener and really like it a lot. However, I like Leo better 
> (plus it's free and open source) and once I figured out how to link to 
> external resources, I never went back to Scrivener. I don't like using 
> LaTEX content auto-generated from something else. I end up spending too 
> much time cleaning it up. For what it's worth, my work flow with LaTEX 
> content is:
>
>1. I mostly write content directly in LaTEX syntax (it's cleaner and 
>easier to edit directly). I created many Leo abbreviations to speed up the 
>process (lists, sections, etc.)
>2. I wrote several outline-data-tree abbreviations to create 'wrapper' 
>shells for different kinds of documents (preambles, etc). Then I simply 
>input the LaTEX content files (\input{content.tex}}.
>3. Since I'm mostly on Windows, I use the excellent TeXnic Center 
> compiler to create the PDF output. (I 
>never use it to edit, only to compile.)
>4. Rarely, if I need to export to something else (xxx.docx or xxx.rtf 
>or xxx.html), I write in multi-markdown and use Pandoc to output.
>
> Excellent post and I'd love to share ideas with other Leo/LaTEX users on 
> work flow. Perhaps I can steal a few better ideas or trade for some of my 
> own.
>
> Rob...
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

How to make Outlines which contains images and can display those images?

[Pal Csanyi]

Hi,

I want to write in Leo editor Outline wich will be contains images too 
beside text.
Moreover, I want to can see those images, that is to be displayed those 
images in Leo editor while I am reading that Otuline.
How can I do that?

Best, Pal

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.