On Mon, 22 May 2017 20:13:13 -0700 (PDT)
Phaze wrote:
> The absence of this feature is the only thing that is preventing me
> from using leo as a password store
This feature exists in the stickynotes plugin. It only works if the
PyCrypto library is installed (python-crypto).
It's per node, not
Check out the stickynote plugin. It has some support for encryption.
I am not sure of its status at the moment though. It has been some time
since I looked at it.
Chris
On Mon, May 22, 2017 at 8:13 PM, Phaze wrote:
> The absence of this feature is the only thing that is preventing me from
> us
The absence of this feature is the only thing that is preventing me from
using leo as a password store
It would be very cool if we could encrypt both the text and the structure
of nodes marked @encrypt and present a dialog box requesting the
key/password to decrypt and use the outline tree. Th
On Mon, 22 May 2017 16:33:22 -0700 (PDT)
Lang Hurst wrote:
> Quick settings question first: Where is the setting to make leo open
> with the last opened file? I am sure that I've looked at it in my
> searches, but I can't seem to find it. The bigger issue is this:
>
> I currently have two noes
Thanks Chris. That works perfectly. I don't know if I would have found it.
I kept searching for "open" "file" and the like. I appreciate it!
On Mon, May 22, 2017 at 4:51 PM, Chris George wrote:
> For starting with the exact same files/window settings as last session,
> you need to use the follow
For starting with the exact same files/window settings as last session, you
need to use the following command line options.
launchLeo.py --session-restore --session-save
Chris
On Mon, May 22, 2017 at 4:33 PM, Lang Hurst wrote:
> Quick settings question first: Where is the setting to make leo o
Quick settings question first: Where is the setting to make leo open with
the last opened file? I am sure that I've looked at it in my searches, but
I can't seem to find it. The bigger issue is this:
I currently have two noes that I'll say look like this:
node_A: node_B:
Bana
On Monday, May 22, 2017 at 2:39:01 PM UTC-5, Edward K. Ream wrote:
> gitk --since="4/18/2017" leo\core\leo*.py
...
> I'll give this last set of diffs a look-see.
There's nothing of great interest. As expected, most changes involved
tracing and headline comments. Here are the most important cha
On Monday, May 22, 2017 at 11:21:25 AM UTC-5, Edward K. Ream wrote:
>
> On Mon, May 22, 2017 at 10:49 AM, Terry Brown
> wrote:
>
>> how many changes to
non-curses Leo code has the project required?
> None of any consequence...Most other changes involved improved traces.
See for yourself.
On Mon, May 22, 2017 at 10:49 AM, Terry Brown wrote:
> On Mon, 22 May 2017 08:00:12 -0700 (PDT)
> "Edward K. Ream" wrote:
>
> > *Important warning*This project is entering its* most dangerous*
> > phase users. The possiblity for data loss is large. This is a direct
> > consequence of the progres
On Mon, 22 May 2017 08:00:12 -0700 (PDT)
"Edward K. Ream" wrote:
> *Important warning*This project is entering its* most dangerous*
> phase users. The possiblity for data loss is large. This is a direct
> consequence of the progress that is being made.
I assume this risk is limited to people tes
On Monday, May 22, 2017 at 10:00:12 AM UTC-5, Edward K. Ream wrote:
> As the code really begins to *look like* it works, you must *use extreme
caution* while trying it out. Please test the cursesGui2 plugin out only on
expendable files, or files under git control.
Imo, the only sane strategy fo
On Sunday, May 21, 2017 at 6:17:32 AM UTC-5, Edward K. Ream wrote:
> ...all tests run with 21 failures and 3 errors.
*Just now:*
Ran 901 tests in 26.473s
FAILED
(failures=3, skipped=38)
These three failures are real, but minor problems. They can be ignored for
now. There are much bigger fish t
13 matches
Mail list logo
