Re: Strategy for #165: vim-open-file

Latest version of Leo: commit = 014cfd569ad8 If you do vim-open-node on two different nodes, the first opens without a problem. Trying to open the second node produces the following error: unexpected exception in c.openWith Traceback (most recent call last): File "c:\users\szatz\leo-editor\le

Re: Strategy for #165: vim-open-file

May 2, 2015 at 6:07 PM, Edward K. Ream wrote: > > > On Sat, May 2, 2015 at 7:43 AM, Steve Zatz wrote: > >> So far no luck but am wondering if the error below is causing subsequent >> plugins to fail to load. >> > > A failed plugins should not affect other plugins. &

Re: Strategy for #165: vim-open-file

So far no luck but am wondering if the error below is causing subsequent plugins to fail to load. A related question is: there are a number of plugins that appear to load automatically -- how can that list be modified since I don't see them in any settings file? The error is: Traceback (most re

Re: Strategy for #165: vim-open-file

Thu, Apr 30, 2015 at 1:54 PM, Edward K. Ream wrote: > > > On Wed, Apr 29, 2015 at 11:43 AM, Steve Zatz wrote: > >> > 3 versions exist, Leo buffer, vim buffer and disk version... >> >> I do think that the other capability you want is to be able to open a >>

Re: Strategy for #165: vim-open-file

> 3 versions exist, Leo buffer, vim buffer and disk version... Yep. So you are correct that simultaneous changes to both the vim buffer and leo buffer will conflict but whichever app next saves its buffer, the other app will notify the user and ask whether to refresh or not. That works for me ev

Re: Strategy for #165: vim-open-file

A few weeks ago I believe that open-with worked as described above. It opened the file of the highlighted @file/@clean file. Separately, an @file/@clean that is modified outside of Leo does trigger Leo to ask whether the file should be updated or not. What has changed with some revision is open-

Re: Flat file view

> Please file an enhancement request. I'll target it for 5.1 b2. Enhancement Request thanks, Steve -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop rec

Re: Flat file view

Separate from however vim-open-file works, could leo routinely (or have an @settings switch) track externally referenced files for changes since the last leo-initiated save and alert the user that a file has been changed outside leo? This is done on startup of leo but there doesn't appear to be on

Re: Flat file view

and fills an important gap in capability. > > Thanks, > Kent > > (what about 'Open with' appearing on node rclick menu ...?) > > On Thu, Mar 26, 2015 at 4:39 PM, Steve Zatz wrote: > >> Do you use it? does it operate on nodes? > >> Seeing it on the '

Re: Flat file view

> Do you use it? does it operate on nodes? > Seeing it on the 'File' menu, it looks to be intended only for files, not nodes. Works perfectly. @settings->@openwwith Vim node contents are simply: ext: kind: subprocess.Popen arg: (location of vim executable) Sounds like it would open the whole

Re: Flat file view

I am sure this is obvious, but with regard to vim, what does the vim plugin do that just making an @settings -> @openwith Vim doesn't do? Steve On Thu, Mar 26, 2015 at 6:07 AM, Edward K. Ream wrote: > > > On Wed, Mar 25, 2015 at 6:00 AM, Kent Tenney wrote: > >> Correction, in /tmp/vim_leo.brid

Re: In praise of @clean ... and a question

report since it should be the same as using recursiveImport, correct? Steve On Mon, Mar 9, 2015 at 6:54 AM, Edward K. Ream wrote: > On Sun, Mar 8, 2015 at 8:22 PM, Steve Zatz wrote: > >> This is a relatively long post in praise of @clean (with one question at >> the end)

In praise of @clean ... and a question

This is a relatively long post in praise of @clean (with one question at the end) in case anyone wants to move on to other topics. I just want to provide my own thoughts about the importance of @clean. I look at the posts in this group a fair amount because I find the discussion interesting but I

Re: @nosent issue

> Are the .py and .leo files in the same directory? > Please set ​to True in at.readOneAtNosentNode and report the results printed to the console. Thanks. The .py and .leo files are in the same directory. I assume you meant to set trace = True. I sent the console output to your email. Steve --

Re: @nosent issue

I have executed clear-all-caches and have started leo with --no-cache. I continue to get the log file below and the leo outline that is created has the first class in the file and all it's subnodes but does not have any of the subsequent classes in the file. In other words, I have two nodes under

Re: @nosent issue

Line 2090 is: #@check_task_selected The #@xxx was a shorthand - I mistakenly thought that was obvious. They are commented out decorators. If you don't see them, then I am confused. On Mon, Feb 16, 2015 at 5:55 AM, Edward K. Ream wrote: > On Sunday, February 15, 2015 at 6:15:45 AM UTC-6, Stev

Re: @nosent issue

> Please send me the .leo file and external file so I can track down what is happening. Sent. On Sun, Feb 15, 2015 at 1:29 PM, Edward K. Ream wrote: > On Sun, Feb 15, 2015 at 11:55 AM, Steve Zatz wrote: > >> > Thanks for this. The fix is at rev 16981fd. All tests pass. &

Re: @nosent issue

> Thanks for this. The fix is at rev 16981fd. All tests pass. Unfortunately, not fixed but a different log message. I no longer get the listing of the old and new sentinels but I still get the message that the input file is corrupted and I don't get any of the classes after the first (which does

@nosent issue

I have a python file with a couple of lines that look like: #@ I am not 100% sure this is the problem but if you look at the log file below (edited to shorten it), the only difference between the first and second set of sentinels is the indentat

Re: Vim emulation: ready for testing!

Ream wrote: > On Fri, Aug 15, 2014 at 9:54 PM, Steve Zatz wrote: > > With traces enabled and vim-mode = True, in normal mode and no other > > settings active, typing a colon produces the following on the console: > > > > masterKeyHandler stroke: char: u':' c

Re: Vim emulation: ready for testing!

With traces enabled and vim-mode = True, in normal mode and no other settings active, typing a colon produces the following on the console: masterKeyHandler stroke: char: u':' ch: u':' state None state2 insert ignore masterKeyHandler,do_key,do_normal_mode,do_state setLabel ' Normal: ' do_state,i

Re: Vim emulation: ready for testing!

n Fri, Aug 15, 2014 at 5:52 AM, Edward K. Ream wrote: > On Thu, Aug 14, 2014 at 7:10 PM, Steve Zatz wrote: > > I followed the directions although I wasn't sure what ekr.leo was so I > just > > created a new test.leo and inserted the vim = true @ setting in that new

Re: Vim emulation: ready for testing!

> > Windows 7 AMD64 (build 6.1.7601) SP1 > > > I didn't run with an empty config, though. > -->Jake > > > On 8/14/2014 8:10 PM, Steve Zatz wrote: > > I followed the directions although I wasn't sure what ekr.leo was so I > just created a new test.leo a

Re: Vim emulation: ready for testing!

[D] wholeword = True legend: leoSettings.leo [D] default settings [F] loaded .leo File [M] myLeoSettings.leo On Thu, Aug 14, 2014 at 4:37 PM, Edward K. Ream wrote: > On Thu, Aug 14, 2014 at 2:56 PM, Edward K. Ream > wrote: > > On Thu, Aug 14, 2014 at 11:41 AM, Steve Zatz wrot

Re: Vim emulation: ready for testing!

reading settings in c:\home\slzatz\test.leo This is consistent with the fact that my version of Leo now looks like a dos application. ;-) On Thu, Aug 14, 2014 at 8:53 AM, Edward K. Ream wrote: > On Thu, Aug 14, 2014 at 6:44 AM, Steve Zatz wrote: > > > I am typing a colon --

Re: Vim emulation: ready for testing!

works is frustrating and if I could use vim-style bindings it would be a major advance. Steve On Thu, Aug 14, 2014 at 7:13 AM, Edward K. Ream wrote: > On Wed, Aug 13, 2014 at 8:33 PM, Steve Zatz wrote: > >> recommend looking at the output of the print-bindings and > print-sett

Re: Vim emulation: ready for testing!

nsert-newline tree: Right expand-and-go-right text: Right forward-char Tab newline-and-indent tree: Upgoto-prev-visible text: Upprevious-line On Wed, Aug 13, 2014 at 11:25 AM, Edward K. Ream wrote: > On Wed, Aug 13, 2014 at 6:16 AM, Steve Zatz wrot

Re: Vim emulation: ready for testing!

s not entirely clear to me and I haven't touched the latter. On Wed, Aug 13, 2014 at 6:22 AM, Edward K. Ream wrote: > On Tue, Aug 12, 2014 at 10:05 PM, Steve Zatz wrote: > > Not giving up yet. > > > > Completely clean Leo install from git. > > > > Only nod

Re: Vim emulation: ready for testing!

Not giving up yet. Completely clean Leo install from git. Only nodes in myLeoSettings are setting vim-mode to true and placing the @keys Vim bindings under @settings A bunch of normal mode vim bindings work. Typing a colon produces the following on the windows command line: ignore masterKeyHan

Re: Summary of vim mode: please test it now

ng key bindings in myLeoSettings.leo all u undo tree u enter-tree-undo-mode I have not done much with Leo's key bindings in general so how to sort this out is a bit mysterious and I'd appreciate any pointers. Thanks. -- Steve On Mon, Aug 11, 2014 at 9:55 PM, Edward K. Ream wrote: > On Mon,

Re: Summary of vim mode: please test it now

and-line mode? On Mon, Aug 11, 2014 at 6:11 PM, Edward K. Ream wrote: > On Mon, Aug 11, 2014 at 3:23 PM, Steve Zatz wrote: > > When I type a colon in normal > > mode, still nothing happens (meaning it stays in vim normal mode) except > now > > "ignoring semico

Re: Summary of vim mode: please test it now

Still having problems with vim-mode although they are evolving. I am on Windows 7 with the latest code and followed the instructions for enabling vim mode and it continues to work partially. When I type a colon in normal mode, still nothing happens (meaning it stays in vim normal mode) except now

Re: Vim emulation: ready for testing!

I may be doing something wrong but when I type a colon in normal mode nothing is happening. When I type :q, nothing happens except the log file prints "not ready vim_q". Besides setting @bool vim-mode = True, do I need to do anything else? Steve On Thu, Aug 7, 2014 at 1:21 PM, Edward K. Ream

Re: Vim emulation: ready for testing!

Sounds like great progress and I'm not sure that this would be helpful at this stage but it's interesting that there has been recent work to make FakeVim accessible from PyQt. https://github.com/hluk/FakeVim https://github.com/hluk/FakeVim/issues/5 --Steve -- You received this message because

Re: opening new top level windows

> Setting the stylesheet for the entire QTextBrowser widget sets the colors for the scrollbars. > That is a Qt bug, and is unacceptable visually. I haven't looked at the Leo code but this seemed relevant. http://stackoverflow.com/questions/9554435/qtextedit-background-color-change-also-the-color-

Re: Oh, the irony

> The day is coming when I'll introduce myself to David Beazley... A pretty interesting brief history of Swig posted by Beazley recently. Best quotation may be: "I think the complexity of Swig has exceeded anyone's ability to fully understand it (including my own)." Link to full post below: htt

Re: Rich text editing in Leo

> Also note that I get the following message in the console when I use > stickynotesplus on the @enabled-plugins node in test.leo: Yes -- note that markdown syntax uses characters like #,* and indentation so applied to a random pre-existing Leo node, it will generally produce errors (as would rst

Rich text editing in Leo

This is really a proof of concept but seems to work well in the 10 minutes I've used it :-). I hope it's of interest. I was inspired by Ville's stickynote plugin since I have always wanted to have Leo notes with rich text (a little more than in Ville's proof-of-concept). So I have modified Ville

Problem creating new .leo file

Bzr pull from about an hour ago: Leo Log Window Leo 4.7 devel, build 2277, August 28, 2009 Python 2.6.4, qt version 4.5.2 linux2 reading: /home/slzatz/sticky.leo reading: @thin /home/slzatz/leo-editor/leo/plugins/stickynotes_plus.py exception executing command Traceback (most recent call last):

Re: On rich text editing prototype

> May I assume that the interest in the feature waned Not at all -- I think having rich text capability is very helpful. For my uses, a body pane that contained rst with a toolbar and/or keyboard shortcuts for common formatting and that was transformed to html and displayed as rendered text would

Re: ANN: stickynotes.py plugin

> Just enable qtframecommands.py plugin and run detach-editor-toggle Works as advertised. Thanks. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@go

Re: ANN: stickynotes.py plugin

> Just run detach-editor-toggle again and it will bring back the window. I wonder if I am using an earlier version of the detach/undetach scripts since running either detach or undetach after closing the detached window seems to do nothing and the second time I try it I get this exception ...

Re: ANN: stickynotes.py plugin

Thanks. Works as described and very helpful particularly since with detach/undetach I would constantly close the detached window (by clicking on the close box) and could never figure out how to get back the body edit window. If you can get syntax highlighting working with QPlainTextEdit would be

Re: Any urgent bugs?

> Are there any bugs that require my immediate attention? On Windows, current trunk, the menus still don't work for "comment out" (currently called "add comments") and "uncomment" (currently called "delete comments"). The keyboard equivalents do work. I believe when I checked on Linux one or bo

Scroll position and multiple body editors

Latest trunk. qt gui. I used multiple body editors (2) for the first time in a long time and the scroll position was moving at times that it shouldn't. For example if I scrolled partially down the page and copied some text and then pasted the text somewhere else that was visible without scrolling

Re: Cool hack: detach body editor

> Probably plugin or even core-worthy.Works well and +1 on making it part of the core app. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegrou

Re: Cool hack: detach body editor

> Run this script to create stand-alone window for body editor:Thanks. I think that can be very helpful when you want to focus on the body and/or have a lot of screen real estate. Any way to re-attach it? Steve --~--~-~--~~~---~--~~ You received this message becau

Clone issue

I couldn't get along without Leo but I have been burned by the following a few times. 1) A .leo file has an @thin file named foo. 2) Outside of leo, create a copy of foo, called foo_two 3) Open the original .leo file and import the derived file foo_two into a new @thin node 5) save the .leo file a

Re: Howto: @buttons to change chapters

Thanks for this tip -- works great. > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email t

Re: add/delete comments menu issue

> Could you submit an official bug report in the bug tracker? sure. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe

add/delete comments menu issue

Not a huge issue but with the current trunk -- the menu items for add/delete comments do not appear to do anything but the control-key combinations do work. At some point, you may also want to change the wording since it really is "comment out" and "uncomment" as opposed to add and delete comment

Issue at launch with current trunk

On windows XP, latest trunk -- getting the following: File "C:\home\slzatz\leo-editor\leo\core\leoGlobals.py", line 3570, in doHook return f(tag,keywords) File "C:\home\slzatz\leo-editor\leo\core\leoPlugins.py", line 298, in doPlugins return doHandlersForTag(tag,keywords) File "C:

Re: @shadow and what should I put under version control

> Having the .leo file in version control hurts no one ... But what is the reason to have it in version control? In my mind, it's just an extension of the local code viewer/editor (Leo) and therefore not something that would normally be under version control. And if you get multiple people using

Re: Startup problem

If I create an empty .leo file in my home directory, this problem goes away. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To uns

Startup problem

Clean install on jaunty of current trunk and getting this error: ~/leo-editor$ python launchLeo.py --gui=qt Traceback (most recent call last): File "launchLeo.py", line 8, in leo.core.runLeo.run() File "/home/slzatz/leo-editor/leo/core/runLeo.py", line 88, in run fn,relFn,script = do

Re: Leo questions

Thanks for the quick response. > These are harmless errors - they are tk-only plugins. My biggest problem with the plugins not working is that it is difficult to work with chapters in the qt plugin since the only way to switch among chapters appears to be to use the Select-Chapter command as the

Leo questions

Running the latest trunk on jaunty. If I try to start leo with the qt gui, plugins won't load but at least the application launches. :~$ python /home/slzatz/leo-editor/launchLeo.py --gui=qt foo.leo reading settings in /home/slzatz/leo-editor/leo/config/leoSettings.leo Using menus from leoSetting

Re: Importing an @thin file

Just to close this out (for my own sanity). It is 100% reproducible for me on both Windows and Ubuntu that importing an @thin file initially loads an outline with no detail beyond the top level nodes that exist in the @thin file. If I save the resulting .leo file and then reopen it, the full det

Re: Importing an @thin file

> 1. Create the @thin node, but do **not** save the .leo file. Unfortunately, that didn't work for me either with the qt plugin. If no one else is seeing a problem with either importing or reading @thin files, I'll just assume it's something with my installation. As I've mentioned, the tk versio

Re: Importing an @thin file

> Please explain what you are trying to do, and why simply using an @thin node > won't work. I see I have created some confusion so let me try to be as clear as possible. I am trying to use @thin nodes but I am trying to create them by importing existing @thin files. In more detail -- I work w

Re: Importing an @thin file

> I don't see this behavior, either on Ubuntu or XP. Well that just makes it more interesting ... When I start up Qt Leo I get the following messages (which may have nothing to do with the problem): :~/leo-editor$ python launchLeo.py --gui=qt reading settings in /home/.../leo-editor/leo/config/l

Importing an @thin file

Current trunk, QT plugin, on Ubuntu 8.10. When you import an @thin file using the import derived file command, the file is imported but only top level nodes are present with no nodes appearing under the top level nodes. When I open a .leo file that contains the @thin file, it behaves as expected

Re: Why do at thin files contain file location information?

Thanks much. That looks like it should work since I presume the .leo files on the various platforms accessing the local files under version control can have whatever @path directive they need. Leo is indispensable and this was frustrating so thanks for your help with this. --~--~-~--~---

Why do at thin files contain file location information?

I am sure this is obvious although when I've asked the question previously, there was no answer. The current structure of at thin files contains a sentinel line such as the following: #...@+node:abc.20090106093508.2:@thin /home/jsmith/foo.py If you use subversion and access those at thin fi

Re: Traceback opening .leo file

When I use 4-5-1-2-final and use open recent or save a new .leo file for the first time, I get this same error on both XP and Ubuntu. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to thi

Re: home dir

> home = os.getenv('HOME',default=None) Thanks. That does help. I am no Windows expert but I suspect that on many Windows systems, it is HOMEPATH and HOMEDRIVE that are available and that the HOME environment variable is not set and when that is the case it is the former two that are used to con

home dir

I am sure an obvious question but I don't see documentation related to this. When Leo starts up on Windows, in the log file is written leoID= ABC (in C:\Program Files\Leo\config ) global config dir: C:\Program Files\Leo\config home dir: None How is the "home dir" set and how does it affect Le