Re: Postcards from Leo users

On Thu, 22 Aug 2013 16:06:38 -0500 "Edward K. Ream" wrote: > On Thu, Aug 22, 2013 at 3:42 PM, Terry Brown wrote: > > > > > > Instead of Leo's home page linking the "send us a postcard" to > > > mailto:edream...@gmail.com, I would like the link to create a new > > message > > > > on this thre

Re: Leo 4.11a2 released privately. Please test

Ah, I went back and reinstalled the latest Docutils into python27. Here is the log: Leo Log Window Leo 4.11a1, build 5020, 2012-02-26 13:18:08 -0600 Python 2.7.5, qt version 4.8.5 Windows 6, 1, 7601, 2, Service Pack 1 leoID=lewis (in C:\Users\Lewis\.leo) load dir: C:\Program Files (x86)\Leo-4.11-a

Re: Leo 4.11a2 released privately. Please test

Edward, Re: In other words, this looks like a python problem. Can you get Leo to work with Python 2.6 or 2.7? ' Installing Python 2.7.5 is more successful. Here is the log file for win7-64: Leo Log Window Leo 4.11a1, build 5020, 2012-02-26 13:18:08 -0600 Python 2.7.5, qt version 4.8.

Re: Postcards from Leo users

On Thu, Aug 22, 2013 at 3:42 PM, Terry Brown wrote: > > Instead of Leo's home page linking the "send us a postcard" to > > mailto:edream...@gmail.com, I would like the link to create a new > message > > on this thread. > > > > That wouldn't seem to be too hard. Anyone know how to do that? > >

Re: Postcards from Leo users

On Thu, 22 Aug 2013 13:40:29 -0700 (PDT) "Edward K. Ream" wrote: > On Thursday, August 22, 2013 3:38:33 PM UTC-5, Edward K. Ream wrote: > > > Here is the first postcard, posted here with David's permission: > > Instead of Leo's home page linking the "send us a postcard" to > mailto:edream...@g

Re: Postcards from Leo users

On Thursday, August 22, 2013 3:38:33 PM UTC-5, Edward K. Ream wrote: > Here is the first postcard, posted here with David's permission: Instead of Leo's home page linking the "send us a postcard" to mailto:edream...@gmail.com, I would like the link to create a new message on this thread. That

Postcards from Leo users

Here is the first postcard, posted here with David's permission: I have been using Leo for several years mostly to write LaTeX documents. I used the built-in rst3 facility up until the past few months. However, I kept wanting to do things that I couldn't figure out how to do in rst, so now I

Re: Added rich text support to the printing.py plugin

On Thu, Aug 22, 2013 at 2:42 PM, Fidel Pérez wrote: > Once we are changing the command searching, (btw I also really like the > plugin-starting-name idea), would it be to much resource-cost for the > search to work somewhat like google instant search? > Well, this could be a wishlist item, but I

Re: Control+X vs Control+Shift+X

Posted , glad you found it interesting! On Thursday, August 22, 2013 10:23:23 AM UTC+2, Fidel Pérez wrote: > Hi: > I was thinking that it would be way more intuitive for nodes to be > cut/paste with control+x and control+v instead of having to

Re: Added rich text support to the printing.py plugin

Once we are changing the command searching, (btw I also really like the plugin-starting-name idea), would it be to much resource-cost for the search to work somewhat like google instant search? Well actually we dont need so much, it would just be helpful that if the user doesnt start the search

Re: Leo 4.11a2 released privately. Please test

On Wed, Aug 21, 2013 at 8:10 PM, lewis wrote: > > I think I was tricked by sourceforge; thanks Fidel. Made sure I used the > 4.11-a2 this time. > > It installs to C:\Program Files (x86)\Leo-4.11-a2 but it actually reports > itself as 4.11-a1. > Sorry for the confusion. I've updated the version

Re: Control+X vs Control+Shift+X

On Thu, Aug 22, 2013 at 3:23 AM, Fidel Pérez wrote: > I was thinking that it would be way more intuitive for nodes to be cut/paste with control+x and control+v instead of having to also use Shift. Interesting idea. Please file a wish-list bug. > There is a node/outline on the clipboard (is

Re: Added rich text support to the printing.py plugin

On Thu, Aug 22, 2013 at 8:30 AM, gatesphere wrote: > in fact, I've been thinking of a general suggestion that *all* plugins start their commands with the plugin name, so that we know what came from where. I would suggest that each plugin's commands have a common *prefix*, which may or may not b

Re: Added rich text support to the printing.py plugin

Great idea. If that were true, combined with tab completion, the cognitive load would be reduced to the plugin name. A big win considering the firehose of capability we have to drink from. Thanks, Kent On Thu, Aug 22, 2013 at 8:30 AM, gatesphere wrote: > On 8/21/2013 8:48 AM, Kent Tenney wrote:

Re: Added rich text support to the printing.py plugin

On Thu, 22 Aug 2013 09:30:24 -0400 gatesphere wrote: > I'll think about this... in fact, I've been thinking of a general > suggestion that *all* plugins start their commands with the plugin name, > so that we know what came from where. Ideas? I think that's a good idea which I've sort of trie

Re: Added rich text support to the printing.py plugin

On 8/21/2013 8:48 AM, Kent Tenney wrote: RE: the conflation of command names between printing.py and the print-xxx for informational listings: I suggest the printing.py ones use the 'printing-' prefix. I will never memorize the commands, so tab completion rules. pri brings the command line to

Control+X vs Control+Shift+X

Hi: I was thinking that it would be way more intuitive for nodes to be cut/paste with control+x and control+v instead of having to also use Shift. For this to be possible, cut/paste commands should first pick up if: -There is currently a selected text (either in currently selected header, body,