plugin (nodediff.py) that allows users to diff node
bodies.
It would be cool to integrate this with git (when we move there) so it
compares the body text to the last different previously pushed/committed
version.
EKR
--
You received this message because you are subscribed to the Google
Hi all,
I just pushed a new plugin (nodediff.py) that allows users to diff node
bodies. It's helpful for comparing, say, old and new versions of a
method, or by diffing @edit nodes to act like a traditional diff tool.
Here's the docstring:
Provides commands to run text diffs on node
On Thu, Jan 2, 2014 at 2:15 PM, Jack Kuan kjk...@gmail.com wrote:
Hi,
I'm trying to configure the @string view-rendered-default-kind setting of
the viewrendered plugin, however, since this plugin is enabled by default
in leoSettings.leo
it gets loaded before I have the chance to set
Hi,
I'm trying to configure the @string view-rendered-default-kind setting of
the viewrendered plugin, however, since this plugin is enabled by default
in leoSettings.leo
it gets loaded before I have the chance to set the setting. Is there a way
to update the settings later at runtime? I guess
On 1/2/2014 3:15 PM, Jack Kuan wrote:
Hi,
I'm trying to configure the @string view-rendered-default-kind setting
of the viewrendered plugin, however, since this plugin is enabled by
default in leoSettings.leo
it gets loaded before I have the chance to set the setting. Is there a
way
On Thu, 2 Jan 2014 12:15:57 -0800 (PST)
Jack Kuan kjk...@gmail.com wrote:
Hi,
I'm trying to configure the @string view-rendered-default-kind setting of
the viewrendered plugin, however, since this plugin is enabled by default
in leoSettings.leo
it gets loaded before I have the chance
Hi,
g.es(c.config.getString('view-rendered-default-kind'))
shows md in the log pane. So, I guess it's set correctly, however I'm
unable to preview a node with markdown markups in it unless I make the node
a @md node.
Could this have anything to do with the fact that the plugin sets
ok, after looking at the code, I see that the plugin actually never look at
the setting! It simply determines the kind of node from the headline of the
node or returns self.kind if the headline is not at directive(starts with
@). self.kind is set to 'rst' during plugin init and never gets
a @md node.
Could this have anything to do with the fact that the plugin sets the
option to an attribute rather than getting it from the option setting every
time?
Probably not, all settings should be read with proper precedence before
the plugin starts saving them internally.
gatesphere/Jacob
On 1/2/2014 3:56 PM, Jack Kuan wrote:
ok, after looking at the code, I see that the plugin actually never
look at the setting! It simply determines the kind of node from the
headline of the node or returns self.kind if the headline is not at
directive(starts with @). self.kind is set to 'rst
Peck wrote:
On 1/2/2014 3:56 PM, Jack Kuan wrote:
ok, after looking at the code, I see that the plugin actually never
look at the setting! It simply determines the kind of node from the
headline of the node or returns self.kind if the headline is not at
directive(starts
, January 2, 2014 4:14:46 PM UTC-5, Jacob Peck wrote:
On 1/2/2014 3:56 PM, Jack Kuan wrote:
ok, after looking at the code, I see that the plugin actually never
look at the setting! It simply determines the kind of node from the
headline of the node or returns self.kind
with bzr, so I'm not going to live on the bleeding edge
just yet, but I'm happy with my fix so far.
Thanks
Jack
On Thursday, January 2, 2014 4:14:46 PM UTC-5, Jacob Peck wrote:
On 1/2/2014 3:56 PM, Jack Kuan wrote:
ok, after looking at the code, I see that the plugin actually never
look
On 1/2/2014 4:35 PM, Jack Kuan wrote:
Will do! Appreciate the help!
Thanks
No problem :)
--Jake
--
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
On Fri, Dec 20, 2013 at 10:13 AM, gatesphere gatesph...@gmail.com wrote:
As requested on IRC, here are new plugin release notes that I'm aware of.
Thanks. These notes helped a lot.
Edward
--
You received this message because you are subscribed to the Google Groups
leo-editor group
As requested on IRC, here are new plugin release notes that I'm aware of.
New plugins:
- nodewatch.py... I can't explain it terribly well, please see the
docstring. Basically it's a scriptable jump-list of nodes with a UI
pane. Yet another option instead of clones/bookmarks/backlinks/UNLs
Not sure if hanging from the same branch, but Terry recently changed
bookmarks plugin too, to include inter-file functionality.
--
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
! Forget that C-style comments don't
nest. Big trouble!
- [Too big] Stylesheets contain too much. @data
qt-gui-user-plugin-style-sheet helps.
But not much. For example, print-settings just shows the entire
stylesheet, which is no help at all.
- [Special case] Stylesheets are unlike any
global, serious, repercussions.
Misplace that semicolon? Trouble! Forget that C-style comments don't
nest. Big trouble!
- [Too big] Stylesheets contain too much. @data
qt-gui-user-plugin-style-sheet helps.
But not much. For example, print-settings just shows the entire
code] This is a relative term ;-)
Cons:
- [Fragile] Errors in stylesheets can have global, serious, repercussions.
Misplace that semicolon? Trouble! Forget that C-style comments don't
nest. Big trouble!
- [Too big] Stylesheets contain too much. @data
qt-gui-user-plugin-style-sheet helps
term ;-)
Cons:
- [Fragile] Errors in stylesheets can have global, serious, repercussions.
Misplace that semicolon? Trouble! Forget that C-style comments don't
nest. Big trouble!
- [Too big] Stylesheets contain too much. @data
qt-gui-user-plugin-style-sheet helps
@others
would be more consistent.
Do we need both @others and references ? Hopefully there's a
simple call to get the text from a node that accounts for both @others
and references , so maybe it doesn't matter.
From my printing.py plugin (not sure how I figured it out!):
def untangle(self,p
On Wed, Dec 4, 2013 at 10:00 AM, Terry Brown terry_n_br...@yahoo.comwrote:
On Wed, 4 Dec 2013 04:10:03 -0800 (PST)
Edward K. Ream edream...@gmail.com wrote:
Here, I'll summarize the pros and cons of style sheets, and throw out an
alternative for discussion.
So, that's not really an
On Sat, Nov 23, 2013 at 2:47 PM, Fidel N fidelpe...@gmail.com wrote:
Hey, this is my first screencast ever and I didnt buy camstasia like
Edward hehe.. so just tell me if its clear enough or I should repeat it
making more emphasis in any of the steps.
Thanks for this. It's on the list to
I played around with this bookmarks feature and I like it. Thanks
Terry (and whoever else was involved).
However, I didn't like how the mod_http server binds to all IP
interfaces. This means anyone anywhere could browse your open Leo
outlines (and add bookmarks), if they know your assigned IP
Hey, this is my first screencast ever and I didnt buy camstasia like Edward
hehe.. so just tell me if its clear enough or I should repeat it making
more emphasis in any of the steps.
http://www.youtube.com/watch?v=9AvbL_0JEMwfeature=youtu.be
--
You received this message because you are
And here is the Leo file I talk about in the video.
--
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,
I installed this a couple of days ago and it worked for me. I came back to
it today to try the One Tab functionality and it throws this error. And I
cannot get it to work at all.
** isPython3: False
Leo 4.11 final, build 6367, 2013-11-23 06:21:51
Python 2.7.4, qt version 4.8.4
linux2
setting
@string rst_http_attributename = 'rst_http_attribute'
I'm not sure what that last parameter does
In the old plugin (pre-tabs), I noticed that if I move my cursor to a new
location, the bookmark is saved there. I.e. it isn't always at the root
node.
May not be a problem/ feature
challenge. More videos will follow to deal with other niceties.
A couple of mysteries:
@settings
@bool http_active = True
@int http_port = 8080
@string rst_http_attributename = 'rst_http_attribute'
I'm not sure what that last parameter does
In the old plugin (pre-tabs), I
Thanks for the video
Glad this was helpful.
It still bookmarks individual pages properly, just fails on the onetab page.
The javascript text changed, so you should have created a new bookmark with
the updated javascript included in the attached leo file, its this one:
Thanks Fidel, that works great now.
Chris
On Saturday, November 23, 2013 3:56:40 PM UTC-8, Fidel N wrote:
Thanks for the video
Glad this was helpful.
It still bookmarks individual pages properly, just fails on the onetab
page.
The javascript text changed, so you should have created a
It seems there is a limit to how many open tabs it can deal with. Do we
know what that number is? I was trying to have it deal with 40 open tabs. I
tried it with 3 and it worked great.
Chris
On Saturday, November 23, 2013 4:45:31 PM UTC-8, Chris George wrote:
Oops, no it didn't work.
Oops, no it didn't work.
Traceback (most recent call last):
File /home/chris/Working/leo/leo-editor/leo/plugins/mod_http.py, line
570, in send_head
f = self.leo_actions.get_response()
File /home/chris/Working/leo/leo-editor/leo/plugins/mod_http.py, line
1130, in get_response
return
The error you are getting is not related to the number of pages but to the
encoding of the name on some of the pages.
For example, if one of the websites contains an Ñ, and the decoding is
not ready for that, the script fails and throws an unicode error.
Lets wait for Terry to give us a word
I isolated it to or . If either of them exist in the title of the
page, the script crashes.
Chris
On Saturday, November 23, 2013 4:56:27 PM UTC-8, Fidel N wrote:
The error you are getting is not related to the number of pages but to the
encoding of the name on some of the pages.
For
On Sat, 23 Nov 2013 16:45:31 -0800 (PST)
Chris George technat...@gmail.com wrote:
UnicodeDecodeError: 'utf8' codec can't decode byte 0xbb in position 0:
I'll try and fix this tomorrow.
Cheers -Terry
--
You received this message because you are subscribed to the Google Groups
leo-editor
On Fri, Nov 1, 2013 at 1:47 PM, Jacob Peck gatesph...@gmail.com wrote:
New plugin up on Launchpad. Here's the docstring:
Provides a GUI in the Log pane (tab name 'Nodewatch') that lists node
headlines.
The nodes that show up in this GUI are scriptable on a per-outline basis
On 11/4/2013 11:41 AM, Edward K. Ream wrote:
On Fri, Nov 1, 2013 at 1:47 PM, Jacob Peck gatesph...@gmail.com
mailto:gatesph...@gmail.com wrote:
New plugin up on Launchpad. Here's the docstring:
Provides a GUI in the Log pane (tab name 'Nodewatch') that lists
node
On 11/4/2013 11:41 AM, Edward K. Ream wrote:
On Fri, Nov 1, 2013 at 1:47 PM, Jacob Peck gatesph...@gmail.com
mailto:gatesph...@gmail.com wrote:
New plugin up on Launchpad. Here's the docstring:
Provides a GUI in the Log pane (tab name 'Nodewatch') that lists
node
On Fri, Oct 18, 2013 at 7:37 AM, lewis lewisn...@operamail.com wrote:
I believe the leo_to_html plugin output can be improved.
Feel free to file a bug report. I didn't write this plugin, and have no
plans to change it.
Edward
--
You received this message because you are subscribed
Hi all,
New plugin up on Launchpad. Here's the docstring:
Provides a GUI in the Log pane (tab name 'Nodewatch') that lists node
headlines.
The nodes that show up in this GUI are scriptable on a per-outline
basis, with @nodewatch
nodes.
By Jacob M. Peck
@nodewatch Nodes
I've just pushed some changes to todo.py, nothing fundamental, but if
these changes mess up anyone's workflow, let me know and I'll try and
wrap them in @settings.
- date selection - custom calendar widget which displays multiple
months at a time. By default it shows the next three months,
On Mon, Oct 21, 2013 at 9:01 AM, Terry Brown terry_n_br...@yahoo.comwrote:
I've just pushed some changes to todo.py,
Thanks for this work, Terry.
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To unsubscribe from this group and stop receiving
On Sat, 19 Oct 2013 11:43:01 -0700
Chris George technat...@gmail.com wrote:
Hi Edward,
I made the request and the plugin is called markup_inline.
It takes over Ctrl-I for italic and Ctrl-B for bold. The Ctrl-U for
Actually it just provides markup-inline-bold, markup-inline-italic
When I first read the request, from I don't remember who, for key binding
for character-formatting markup I thought, this is such a small matter.
I've changed my mind. As I have been working on the docs, I am continually
reminded that it would be just slightly easier to use a single keystroke
Hi Edward,
I made the request and the plugin is called markup_inline.
It takes over Ctrl-I for italic and Ctrl-B for bold. The Ctrl-U for
underline never worked for me but I never use it anyway. It does disable
the functionality that was previously assigned to these keys but it is a
muscle
I believe the leo_to_html plugin output can be improved.
Create a test file with rST table data:
== == == ==
Col A Col B Col C Col D
== == == ==
2A 2B 2C 2D
3A 3B 3C 3D
== == == ==
If you export from Leo using
This plugin has been updated as of rev 6139 to make it more
configurable. Here's the relevant section of the docstring:
Configuration Settings
==
This plugin is configured with the following @settings:
@string rss-date-format
---
Format
Hello Jake
Am Samstag, 5. Oktober 2013 00:01:54 UTC+2 schrieb Jacob Peck:
On 10/4/2013 5:18 PM, Edward K. Ream wrote:
On Thu, Oct 3, 2013 at 9:47 AM, Jacob Peck gates...@gmail.comjavascript:
wrote:
Rev 6095 pushes a new plugin that I hacked together over the past few
hours
plugin that I hacked together over the
past few hours, adding primitive RSS reader behavior to Leo.
It requires the 'feedparser' module to be installed.
Cool! Thanks for this work. I've put it on the list of things
to look at asap.
Edward
Thanks! After using
plugin that I hacked together over the
past few hours, adding primitive RSS reader behavior to Leo.
It requires the 'feedparser' module to be installed.
Cool! Thanks for this work. I've put it on the list of things
to look at asap.
Edward
Thanks! After using
Peck gates...@gmail.com wrote:
Rev 6095 pushes a new plugin that I hacked together over the past few
hours, adding primitive RSS reader behavior to Leo. It requires the
'feedparser' module to be installed.
Cool! Thanks for this work. I've put it on the list of things to look
On Thu, Oct 3, 2013 at 9:47 AM, Jacob Peck gatesph...@gmail.com wrote:
Rev 6095 pushes a new plugin that I hacked together over the past few
hours, adding primitive RSS reader behavior to Leo. It requires the
'feedparser' module to be installed.
Cool! Thanks for this work. I've put
On 10/4/2013 5:18 PM, Edward K. Ream wrote:
On Thu, Oct 3, 2013 at 9:47 AM, Jacob Peck gatesph...@gmail.com
mailto:gatesph...@gmail.com wrote:
Rev 6095 pushes a new plugin that I hacked together over the past
few hours, adding primitive RSS reader behavior to Leo. It
requires
I get this plugin message using build 6101
Leo Log Window
Leo 4.11a3, build 6101, 2013-10-05 08:35:33
Python 3.3.2, qt version 4.8.5
Windows 6, 1, 7601, 2, Service Pack 1
Abbreviations off
syntax error importing plugin: leo.plugins.todo
loadOnePlugin: can not load enabled plugin: leo.plugins.todo
On Fri, 4 Oct 2013 17:00:08 -0700 (PDT)
lewis lewisn...@operamail.com wrote:
I get this plugin message using build 6101
Leo Log Window
Leo 4.11a3, build 6101, 2013-10-05 08:35:33
Python 3.3.2, qt version 4.8.5
Windows 6, 1, 7601, 2, Service Pack 1
Abbreviations off
syntax error importing
Hi all,
Rev 6095 pushes a new plugin that I hacked together over the past few
hours, adding primitive RSS reader behavior to Leo. It requires the
'feedparser' module to be installed.
Here's the docstring:
Adds primitive RSS reader functionality to Leo.
By Jacob M. Peck.
RSS
I made a node in myLeoSettings.leo: @enabled-plugins. The text for this
node is just vim.
I also edited the nodes under vim plugin in leoSettings.leo to @@string
vim_cmd = C:\Program Files (x86)\Vim\vim73\gvim --servername LEO and
@@string vim_exe = C:\Program Files (x86)\Vim\vim73\gvim
On Thu, Sep 12, 2013 at 5:14 PM, Stephen Boulet stephen.bou...@gmail.comwrote:
I made a node in myLeoSettings.leo: @enabled-plugins. The text for this
node is just vim.
It should be vim.py, the name of the plugin's .py file.
Edward
--
You received this message because you are subscribed to
On Fri, Aug 23, 2013 at 3:13 PM, Kent Tenney kten...@gmail.com wrote:
I'll stop now.
I find your point of view unconvincing, for the following reasons:
1. The docstring of any plugin should tell the commands provided by that
plugin. It is easy to read that docstring using the plugins menu
On Monday, August 26, 2013 6:24:34 AM UTC-5, Edward K. Ream wrote:
As I write this, however, I discover that F12 does not work for any vr
commands.
Well, there is no help for misreading the tab completion data.
help-for-command is working just fine.
F12 is bound to help-for-python, not
stop now.
I find your point of view unconvincing, for the following reasons:
1. The docstring of any plugin should tell the commands provided by that
plugin. It is easy to read that docstring using the plugins menu.
2. The help-for-command command (default binding F12) should tell enough
about
On Mon, Aug 26, 2013 at 8:14 AM, Kent Tenney kten...@gmail.com wrote:
I'm coming out of retirement on this thread, only to address
what appears to be a misunderstanding:
Although heroic improvements to tab completion are possible
The suggestion regarding making any changes to tab completion
On Thu, Aug 22, 2013 at 1:46 PM, Edward K. Ream edream...@gmail.com wrote:
On Thu, Aug 22, 2013 at 8:30 AM, gatesphere gatesph...@gmail.com 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
On Fri, Aug 23, 2013 at 9:03 AM, Kent Tenney kten...@gmail.com wrote:
I would suggest that each plugin's commands have a common *prefix*, which
may or may not be the name of the plugin.
Which requires remembering which are and which are not prefixed by the
plugin name.
The tension
commands as a part of the printing.py
plugin:
print-selected-node-body-html
---
Opens up the print dialog to print the body of the selected node as a
rendered HTML (i.e., rich text) document.
print-preview-selected-node-body-html
---
Opens up the print preview dialog to preview
from the viewrendered
plugin. But Edward doesn't want to have to type vitabrtab, which
is what I think you've have to type to get 'viewrendered' (currently
'vr'), because I imagine vitab would give you the view-lossage
command, whatever that is.
Cheers -Terry
Cheers.
On Wednesday, August 14
On Fri, Aug 23, 2013 at 2:55 PM, Fidel Pérez fidelpe...@gmail.com wrote:
Im sorry to insist but it looks to me that I dint express well what I
meant. English is not my mother language and sometimes Im not sure I
expressed correctly what I wanted to share.
Well, English is my mother language,
On Fri, Aug 23, 2013 at 1:50 PM, Edward K. Ream edream...@gmail.com wrote:
On Fri, Aug 23, 2013 at 9:03 AM, Kent Tenney kten...@gmail.com wrote:
I would suggest that each plugin's commands have a common *prefix*,
which
may or may not be the name of the plugin.
Which requires remembering
Hehe thanks both for the clarification and patience.
Iirc, I asked you to file a wish-list bug. Please do so if you haven't
already.
On my way!
On Friday, August 23, 2013 10:09:40 PM UTC+2, Edward K. Ream wrote:
On Fri, Aug 23, 2013 at 2:55 PM, Fidel Pérez fidel...@gmail.comjavascript:
the command line to 'print-' and
an additional 'i' would be sufficient to limit the choices to commands
relating to printing.py
Thanks,
Kent
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
On Thu, 22 Aug 2013 09:30:24 -0400
gatesphere gatesph...@gmail.com 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
On Thu, Aug 22, 2013 at 8:30 AM, gatesphere gatesph...@gmail.com 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
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
On Thu, Aug 22, 2013 at 2:42 PM, Fidel Pérez fidelpe...@gmail.com 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
of the printing.py
plugin:
print-selected-node-body-html
So this is really useful - about the only time I'd use OpenOffice
Writer would be when I wanted to print something with 20pt
text on it, to make a sign to stick on a wall or something.
You can do it with plain text and enscript, but I
On Wed, Aug 14, 2013 at 2:25 PM, Jacob Peck gatesph...@gmail.com wrote:
Rev 5904 adds the following two commands as a part of the printing.py
plugin:
print-selected-node-body-html
...
print-preview-selected-node-**body-html
And I see you've updated the doc string so people will find them
On 8/20/2013 10:56 PM, Terry Brown wrote:
On Wed, 14 Aug 2013 15:25:42 -0400
Jacob Peck gatesph...@gmail.com wrote:
Rev 5904 adds the following two commands as a part of the printing.py
plugin:
print-selected-node-body-html
So this is really useful - about the only time I'd use OpenOffice
On Wed, 14 Aug 2013 15:25:42 -0400
Jacob Peck gatesph...@gmail.com wrote:
Rev 5904 adds the following two commands as a part of the printing.py
plugin:
print-selected-node-body-html
So this is really useful - about the only time I'd use OpenOffice
Writer would be when I wanted to print
Rev 5904 adds the following two commands as a part of the printing.py
plugin:
print-selected-node-body-html
---
Opens up the print dialog to print the body of the selected node as a
rendered HTML (i.e., rich text) document.
print-preview-selected-node-body-html
---
Opens up the print preview
On Wed, 14 Aug 2013 15:25:42 -0400
Jacob Peck gatesph...@gmail.com wrote:
These commands work nicely with Terry's recent work on the rich-text.py
plugin, allowing users to print a close approximation of the final
results of rich-text nodes.
Great - if you enable all CKEditor's features
(not that I
wish to start a political debate here), perhaps it's not a terrible idea
to write a plugin that hooks into the loading and saving code,
encrypting/decrypting your data?
This could be controlled on a per .leo file basis, perhaps with some
@settings. The algorithm and passkey could
On Fri, Aug 9, 2013 at 7:37 AM, Jacob Peck gatesph...@gmail.com wrote:
In light of recent government-sponsored programs in the US (not that I
wish to start a political debate here), perhaps it's not a terrible idea to
write a plugin that hooks into the loading and saving code,
encrypting
idea to write a plugin that hooks into the loading and
saving code, encrypting/decrypting your data?
Relying on encryption looks hopeless. Today's story:
http://thenextweb.com/insider/2013/08/09/silent-circle-follows-lavabit-in-closing-its-encrypted-email-service-because-it-cannot-be-secure
have multiple encoded nodes, repeat this
process for each one.
In light of recent government-sponsored programs in the US (not that I
wish to start a political debate here), perhaps it's not a terrible idea
to write a plugin that hooks into the loading and saving code,
encrypting
On 8/9/2013 9:38 AM, Terry Brown wrote:
On Fri, 09 Aug 2013 08:37:16 -0400
Jacob Peck gatesph...@gmail.com wrote:
Hello Leonistas,
So, in my groggy hours this morning, an idea struck me. Many (myself
included) use Leo as a PIM. I, for one, use workbook.leo, synced with a
cloud sync
idea to write a plugin that hooks into the loading and
saving code, encrypting/decrypting your data?
Relying on encryption looks hopeless. Today's story:
http://thenextweb.com/insider/2013/08/09/silent-circle-follows-lavabit-in-closing-its-encrypted-email-service-because-it-cannot
here), perhaps it's not a
terrible idea to write a plugin that hooks into the loading and
saving code, encrypting/decrypting your data?
Relying on encryption looks hopeless. Today's story:
http://thenextweb.com/insider/2013/08/09/silent-circle-follows-lavabit-in-closing-its-encrypted-email-service
such services are experts. If they despair, I
have no reason to doubt them.
Having said that, I do not wish to debate which plugins are appropriate.
If you want to do an encryption plugin, go for it.
Edward
--
You received this message because you are subscribed to the Google Groups
leo-editor
-Terry
Having said that, I do not wish to debate which plugins are appropriate.
If you want to do an encryption plugin, go for it.
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
On Fri, Aug 9, 2013 at 12:23 PM, Terry Brown terry_n_br...@yahoo.comwrote:
I'm an ignoramus concerning security and encryption. However, I assume
that web sites that offer such services are experts. If they despair, I
have no reason to doubt them.
I think the problem for the websites /
On Thu, May 16, 2013 at 9:14 AM, Terry Brown terry_n_br...@yahoo.comwrote:
As for prn-, I feel that shortcuts like that are icky when we have full
tab completion.
I agree. The beauty/genius of tab completion is that commands can be as
long as needed.
I vote for using print-* for the new
Im thinking something similar and planning to do so, a pane which will:
- Detect user events and show possible hotkeys according to what he can do
from there (can get the events hook leo already has and whenever one of
those is triggered, the pane changes to show useful hotkeys)
- Its going to
. Can you
elaborate?
I think Kent meant the older commands
print-all-uas
print-bindings
print-buttons
print-commands
print-focus
print-node-uas
print-plugin-handlers
print-plugins-info
print-settings
would be better named list- or show-, so
why you think print-xxx as a
command to send something to a printer is not standard. Can you
elaborate?
I think Kent meant the older commands
print-all-uas
print-bindings
print-buttons
print-commands
print-focus
print-node-uas
print-plugin-handlers
print-plugins-info
-focus
print-node-uas
print-plugin-handlers
print-plugins-info
print-settings
would be better named list- or show-, so as no to intermingle with the
new print-(to the printer) commands.
Cheers -Terry
As a concession, I could rename all of my print- commands
print-buttons
print-commands
print-focus
print-node-uas
print-plugin-handlers
print-plugins-info
print-settings
would be better named list- or show-, so as no to intermingle with
the
new print-(to the printer) commands.
Cheers
Hello all,
I've added a new plugin to Leo, that adds printing support when using
the Qt GUI. Available from rev 5779.
Here's the docscring:
'''Supports printing from the Qt GUI.
Jacob M. Peck, 2013
Commands
This plugin supports the following twelve commands:
print-selected-node
?
On Wed, May 15, 2013 at 7:41 AM, Jacob Peck gatesph...@gmail.com wrote:
Hello all,
I've added a new plugin to Leo, that adds printing support when using the Qt
GUI. Available from rev 5779.
Here's the docscring:
'''Supports printing from the Qt GUI.
Jacob M. Peck, 2013
Commands
601 - 700 of 1500 matches
Mail list logo
