Re: Leo version in log

It' not missing, it's just named 'leo', not 'leo-editor'. Should that matter? Rob... On Saturday, August 3, 2019 at 5:08:52 PM UTC-4, Edward K. Ream wrote: > > > > On Sat, Aug 3, 2019 at 4:02 PM Rob > wrote: > >> Also, I should add the Leo log window's next line shows the current >> directory

Re: Leo version in log

On Sat, Aug 3, 2019 at 4:02 PM Rob wrote: > Also, I should add the Leo log window's next line shows the current > directory as where launchLeo.py and the .git folder reside. Is that the > same thing as cwd? > > > current dir: D:/Synced/github repos/leo > load dir: D:/Synced/github

Re: Leo version in log

Also, I should add the Leo log window's next line shows the current directory as where launchLeo.py and the .git folder reside. Is that the same thing as cwd? Leo Log Window Leo 6.1-devel, devel branch Python 3.7.3, PyQt version 5.9.6 Windows 10 AMD64 (build 10.0.17763) SP0 current dir:

Re: Leo version in log

Did that and confirmed I'm in the cwd. Wondering if it's related to how I get GitHub updates, but don't see a repo setting to change. Rob... > Apparently not. From the powershell prompt, do pwd :-) > > Edward > -- You received this message because you are subscribed to the Google Groups

Re: Leo version in log

On Sat, Aug 3, 2019 at 3:33 PM Rob wrote: > That helps to understand. However, I *am* launching from the main > directory which contains the .git folder. > > I open an Anaconda Powershell prompt in the main Leo directory and invoke > python launchLeo.py. Isn't that then the cwd? > Apparently

Re: Leo version in log

That helps to understand. However, I *am* launching from the main directory which contains the .git folder. I open an Anaconda Powershell prompt in the main Leo directory and invoke python launchLeo.py. Isn't that then the cwd? Rob... On Saturday, August 3, 2019 at 4:17:49 PM UTC-4, Edward

Re: Leo and fossil merged with Rust

Hi, On 30/07/19 10:26 a. m., Matt Wilkie wrote: > > It has been a very long time since I've got this idea of combining > Leo with fossil. For all these years I felt that there was a great > potential in this mixture, but I haven't got the time to do > anything about it until

Re: Leo 6.0 final released

On Sat, Aug 3, 2019 at 11:23 AM Matt Wilkie wrote: gitk shows the following labels on this branch: v6.0, v6.1-dev, >> 6.0-final-rel, master, remotes/origin/6.0-final-rev, >> remotes/origin/master. But not remotes/origin/v6.0. Is that a problem? >> > > I'm seeing the same with gitk and I

Re: Leo version in log

On Sat, Aug 3, 2019 at 3:12 PM Rob wrote: Sorry, but I don't know what 'cwd' means > cwd is the current working directory. It can be affected by how you launch Leo. Your startup script should "cd" (change directory) to the leo-editor directory, which contains the (hidden by default) .git

Re: Huge Aha: org mode/vimoutline champions don't have to transliterate Leo's python code!

On Saturday, August 3, 2019 at 10:02:53 AM UTC-5, Edward K. Ream wrote: *Summary* > > The proposed interaction between org mode (or vimoutline) and Leonine > services is a momentous breakthrough in Leo's history. > > Perhaps only a page or two of elisp (or vimscript) code would be needed, >

Re: Leo version in log

Sorry, but I don't know what 'cwd' means or how to fix it. Is that in a Leo or GitHub setting somewhere? BTW, I use GitHub desktop on both Mac and PC to update Leo (don't use command line). So, why would they be different on two machines when I'm pulling from the same source? Rob... > >

Re: Huge Aha: org mode/vimoutline champions don't have to transliterate Leo's python code!

On Sat, Aug 3, 2019 at 2:02 PM Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > Congrats on this aha :-) > Thank you. 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

Re: Leo version in log

On Saturday, August 3, 2019 at 12:19:44 PM UTC-5, Rob wrote: ​> Why does my Mac Leo log window display the Leo build number and date and the Win10 log not? I get: ​Leo 6.1-devel, devel branch, build 3427d65881 2019-08-02 14:48:24 -0500 Python 3.6.3, PyQt version 5.8.0 Windows 10 AMD64 (build

Re: Emacs features in Leo: general remarks

Hi, On 1/08/19 12:30 p. m., john lunzer wrote: > I don't want to imply that the "buffer" system is almighty (which it > is not) or that Leo should try to emulate it somehow. Buffers are > simply the medium through which emacs executes cohesion. Leo's medium > are trees and nodes. > > While each

Re: Jeff R: What emacs features do you want?

Hi, Just some comments, now that I have the time. On 24/06/19 8:00 a. m., john lunzer wrote: > > > The more one uses emacs the more it becomes obvious that it is not an > editor or an IDE or a PIM, but simply contains all those things. emacs > is not an integrated development environment (IDE)

Re: Leo version in log

Leo 6.1-devel, devel branch, build 3427d65881 Leo 6.1-devel, devel branch, build 3427d65881 Neon Linux based on Ubuntu 18.04 Chris On Sat, Aug 3, 2019 at 10:19 AM Rob wrote: > On my Win10 machine, I get this in the log window: > > Leo 6.1-devel, devel branch > Python 3.7.3, PyQt version

Re: Huge Aha: org mode/vimoutline champions don't have to transliterate Leo's python code!

Congrats on this aha :-) Really glad to see the Leo services coming finally to the picture. It was a long path, but surely a pretty powerful one. Cheers, Offray On 3/08/19 10:13 a. m., Edward K. Ream wrote: > On Saturday, August 3, 2019 at 10:02:53 AM UTC-5, Edward K. Ream wrote: > >

Leo version in log

On my Win10 machine, I get this in the log window: Leo 6.1-devel, devel branch Python 3.7.3, PyQt version 5.9.6 Windows 10 AMD64 (build 10.0.17763) SP0 On my Mac, I get this: Leo 6.1-devel, devel branch, build 3427d65881 2019-08-02 14:48:24 -0500 Python 3.7.4, PyQt version 5.13.0 darwin Both

Re: Leo 6.0 final released

> > gitk shows the following labels on this branch: v6.0, v6.1-dev, > 6.0-final-rel, master, remotes/origin/6.0-final-rev, > remotes/origin/master. But not remotes/origin/v6.0. Is that a problem? > I'm seeing the same with gitk and I honestly don't know if it's a problem. I was hoping you

Re: Huge Aha: org mode/vimoutline champions don't have to transliterate Leo's python code!

On Saturday, August 3, 2019 at 10:02:53 AM UTC-5, Edward K. Ream wrote: *Summary* > > The proposed interaction between org mode (or vimoutline) and Leonine > services is a momentous breakthrough in Leo's history. > > Perhaps only a page or two of elisp (or vimscript) code would be needed, >

Huge Aha: org mode/vimoutline champions don't have to transliterate Leo's python code!

The way is now clear for close integration with Leo and either emacs org mode or vimoutline. Similar remarks apply to both, so I'll just discuss org mode here. I have been assuming that supporting Leo in emacs would require transliterating much of Leo's core into elisp. But that's not so!

The next 12 months

I'm always happy to get a new version out the door so that I can begin coding again. It's my first love. I do try to do a bit of planning from time to time, as today's posts show :-) The major items scheduled for 6.1

Thought experiment re IPC

Wouldn't it be great if we could somehow just replace Leo's body pane with pyzo's or vim's. See #990 . Well, that's not going to happen right away, but it might happen in a year or three. A thought experiment shows the problems. Suppose

Emacs is *already* scriptable with python

In another thread I said, "it doesn't seem likely that emacs will ever be scriptable with python. Unless some hero steps up Leo in emacs will remain a tantalizing possibility, just out of reach." Happily I was forgetting pymacs and Leo's bridge

Aha re sharing code

A serious dilemma has been on my mind recently with regard to using pyzo's code. Neither importing nor copying pyzo's code is free from serious problems. Either way, changes to pyzo will ultimately affect Leo. This morning I saw a sideways resolution of this dilemma. Regardless of how Leo

Re: Problems with git push --follow-tags in master

On Sat, Aug 3, 2019 at 6:34 AM Edward K. Ream wrote: I deleted my local "black" branch and then pulled it again. Now all seems well. I was able to: git push --follow-tags but there is still no v6.0 tag on origin/master. Otoh, gitk show the v6.0 tag as yellow, whereas gitk shows the tags

Problems with git push --follow-tags in master

git push --follow-tags [a64] c:\leo.repo\leo-editor>c:\apps\Git\bin\git.exe push --follow-tags To https://github.com/leo-editor/leo-editor.git ! [rejected]black -> black (non-fast-forward) error: failed to push some refs to 'https://github.com/leo-editor/leo-editor.git' hint:

Re: Leo 6.0 final released

On Sat, Aug 3, 2019 at 6:13 AM Edward K. Ream wrote: gitk shows all is well. > For a panicky moment I thought perhaps I hadn't pushed to master, but I did. The latest rev on master is db55bd0, both on my machine and in the master branch . gitk shows

Re: Leo and black

On Fri, Aug 2, 2019 at 4:38 PM Matt Wilkie wrote: > After playing with black for a bit, I quite like it. The only thing I've > seen it change that I haven't wholesale agreed with is dedenting "next line > comments". > This doesn't bother me. In this black issue, amb states: "Comments are not

Re: Leo 6.0 final released

On Fri, Aug 2, 2019 at 4:04 PM Matt Wilkie wrote: > Leo 6.0 final, http://leoeditor.com, is now available on GitHub >> . >> > > I think the v6.0 tag needs to be merged into master branch, or something. > gitk shows all is well. Matt, I see that you