On Monday, February 16, 2015 at 4:22:47 AM UTC-6, Edward K. Ream wrote:
On Sun, Feb 15, 2015 at 2:07 PM, vitalije vitali...@gmail.com wrote:
Leo already has a convention for reading @doc parts when reading @file
nodes...this code is not being used when reading @nosent files.
Just
On Mon, Feb 23, 2015 at 5:10 AM, reinhard.engel...@googlemail.com wrote:
I was suggesting...@plain
...
to avoid the association to 'dirty' or 'changed'.
Interesting. Otoh, plain connotes drab :-) It also clashes slightly with
@language plain.
@plain and @clean have the same number of
Well, I was suggesting to use '@clean' instead of '@plain', to avoid the
association to 'dirty' or 'changed'.
On Saturday, February 21, 2015 at 12:21:33 PM UTC+1, Edward K. Ream wrote:
On Sat, Feb 21, 2015 at 3:21 AM, reinhard...@googlemail.com javascript:
wrote:
Before you go for
On Monday, February 16, 2015 at 1:08:45 PM UTC-6, vitalije wrote:
I have just filled a bug report
https://github.com/leo-editor/leo-editor/issues/138
Fixed at rev 3ee6afd. Let me know if you find any further problems.
EKR
--
You received this message because you are subscribed to the
On Saturday, February 14, 2015 at 3:57:20 AM UTC-6, Edward K. Ream wrote:
Retaining vestigial support for @auto and @shadow means that we are well
ahead of schedule for 5.1b1. I expect to release it in just a few days.
Only @shadow will be deprecated. @auto and its documentation will remain
I am now working on three projects simultaneously: Leo 5.1 (@clean), Leo as
an external diff, and a web-based Leo viewer.
@clean is the most important. It promises a large increase in the number
of people that use Leo. That will increase the usefulness of having a
web-based viewer for Leo.
I am investigating using Leo as an external git diff program. This may
involve adding one or more diff-related command-line arguments to Leo. The
lack of an outline-based diff isn't a big barrier to use Leo, but having an
outline-based diff would be a plus.
Leo already has the capability to
On Wednesday, February 18, 2015 at 9:54:15 AM UTC-6, Edward K. Ream wrote:
I have been wondering whether it would be possible to use xslt to render
.leo files from web pages.
A brief update. My brother speed is working on server-side solutions to
the various problems I mentioned. We want
@clean removes barriers to using Leo that prevented its widespread
adoption. Only now, after the barriers have been removed, do I see how
important those barriers were.
For the very first time, Leo can be used in *all* situations without
compromise. There is no longer any need to make
I have a number of @nosent ...xml files that are triggering node recovery
on read using the most recent Leo pull. It appears that it's trying to
change one of the characters (the divide-by character, summary below):
old: AS ÷
new: AS ÷
Any idea why it's doing this or how to prevent it?
Add the following line to the node::
# -*- coding: utf-8 -*-
This tells Leo the correct encoding to use and all should be well.
Edward
--
That works for python files, but IIRC not for other file types (like
.xml files). Perhaps Leo needs an @encoding directive?
--Jake
--
You received
Try to read in the attached file which contains only one line:
221 Ý
The error message is quite long and I don't know how to copy it from the
terminal window (it doesn't show up in the log pane).
Rob..
On Monday, February 23, 2015 at 12:28:50 PM UTC-5, Largo84 wrote:
That doesn't fix the
On Mon, Feb 23, 2015 at 9:33 AM, Largo84 larg...@gmail.com wrote:
I have a number of @nosent ...xml files that are triggering node recovery
on read using the most recent Leo pull. It appears that it's trying to
change one of the characters (the divide-by character, summary below):
old: AS ÷
???
3. A minor advantage: @file makes Leo files smaller. *Leo stores the entire
@clean *tree* in the .leo file*, but only stores the top-level @file
*node* in the .leo file.
Does this mean to keep alle the files of an entire project in *one* Leo
file?
Did you try this on Leo itself,
Rev c31a7cd adds the surprisingly useful unformat-paragraph command. This
command removes all extra whitespace from a paragraph, which is like the
reverse of the reformat-paragraph command.
Extraneous whitespace causes problems with rST text--various kinds of rST
markup can't be split between
On Mon, Feb 23, 2015 at 10:55 AM, Jacob Peck gatesph...@gmail.com wrote:
That works for python files, but IIRC not for other file types (like .xml
files). Perhaps Leo needs an @encoding directive?
Leo has an encoding directive, and various encoding-related settings.
EKR
--
You received
Try this:
1) Create a new @clean Some.txt node
2) Add the unicode division symbol (÷ on Windows ALT246).
3) Save, close and reopen the file.
4) The ÷ symbol has now been changed to ÷ for some reason.
On a larger scale, I tried saving a larger .txt file containing all of my
shortcuts to various
On Mon, Feb 23, 2015 at 11:49 AM, reinhard.engel...@googlemail.com wrote:
???
Thanks for these questions. Their answers are important. Happily, there
seems to be no significant performance difference between
@file and @clean.
3. A minor advantage: @file makes Leo files smaller.
File C:\Python33\lib\encodings\cp1252.py, line 23, in decode return
codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 5:
character maps to undefined
On Monday, February 23, 2015 at 12:46:20 PM UTC-5, Largo84 wrote:
On Mon, Feb 23, 2015 at 9:08 AM, Edward K. Ream edream...@gmail.com wrote:
Rev c31a7cd adds the surprisingly useful unformat-paragraph command.
+1, thank you!
Matt
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To unsubscribe from this group
20 matches
Mail list logo
