Re: A road to branch pollution: git stash goes back in time

[Xavier G. Domingo]

El 10/07/2017 a las 12:05, Edward K. Ream escribió:

On Sunday, July 9, 2017 at 1:09:57 AM UTC-5, Edward K. Ream wrote:

*Danger*: *stashing goes back in time in master*. All of Leo's
caches must be completely cleared!


And I just came across another danger.  If I have written a file in 
master, I have also written it to /master's/ cache.  Doing git branch 
-b doesn't clear that cache.


As a result, on several occasions I have gotten this:
Internal Leo error in checkForChangedNodes

A workaround is to clear the cache for the affected .leo file.  Not 
sure what the real solution is.


So the conclusion is that Leo's caches must be completely cleared after 
any *git stash* or any *git chechout -b* to make them safe? Is it?


Is this also necessary when doing a simple *git checkout *?

Xavier

--
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, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: leo ftp

[lewis]

There is also the sftp.py plugin written by Jacob Peck. It requires the 
python module 'paramiko' SSH2 protocol library to be installed.

-- 
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, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Vote: display trailing whitespace by default?

[Xavier G. Domingo]

I also vote for the Yes.

Xavier

El 10/07/2017 a las 11:45, Terry Brown escribió:

Hi - I've added a syntax highlighting rule to Leo to display trailing
whitespace, which is the default in some editors, nano for example.

The trailing whitespace is shown underlined with small red dots,
although you can change the color.

So what's the consensus - have this turned on by default, or not?

We can discuss in this list, but if you just want to vote yes or no,
here's a poll:

https://docs.google.com/forms/d/1xrrUYTNcfK6Fvu3_HTEkmzF1O7pPscGwWs9oFxg2Bv0

Cheers -Terry



--
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, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rev 79ba3d: potential crasher in refresh-from-disk

[Edward K. Ream]

On Mon, Jul 10, 2017 at 2:51 PM, vitalije  wrote:

> @Edward, I have noticed that this crasher is still present in several
> branches. I don't know if it will be removed once those branches are merged
> with master. I suppose it will. But watch out that its presence is not
> affecting work on other branches.
>

​Thanks for the reminder.  The typical workflow is to merge master into
each branch before merging the branch into master.  That *should* do the
trick, but vigilance is always good.

I have no idea how all the Linux branches are merged safely...

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 from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: leo ftp

[Edward K. Ream]

On Mon, Jul 10, 2017 at 3:05 PM, Edward K. Ream  wrote:

​I have created ftp2.py by rewriting almost every line of ftp.py. At
present, it's only in the ftp branch.

*Warning*: Imo, neither ftp.py nor ftp2.py is safe to use.

The json provides no way to associate paths on the server with paths in the
file system. This limitation exists with the original ftp.py plugin as
well. Imo, this makes the plugins almost useless.

In ftp2.py, the expected format of the json is:​

[
​  ​
["user-name", "host-name", "password"],
​  ​
["
​filename1"],
​  ​
["
​filename2"]
]

​This must change somehow so that (at least) a common prefix can be
stripped from the file-system paths to yield a server path.

For example, there must be some way to strip away
c:\leo.repo\leo-editor
from the paths on the server.

At present, the ftp2 code uses a hack: it just uses the base name of the
original file.  This will work only for top-level files!

*Improvements*

​
​
​ftp2 carefully and clearly reports all errors.  ftp does not.

ftp2 (probably) uses a different, flatter json representation.  This is
easier to use, but a bit less flexible.

ftp2 updates the @data ftp node with timestamp data.  ftp also does this,
but ftp2 pretty-prints the results.​

Coming:

1. (Essential) Change the json representation as discussed above.

2. (Essential) A real docstring.

3. (Important) The ftp2 plugin will use an ftp-upload command rather than
an icon.

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 from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: leo ftp

[Edward K. Ream]

On Monday, July 10, 2017 at 2:31:21 PM UTC-5, Edward K. Ream wrote:

> the real need is a proper docstring

json is not python it's much pickier:

- Comments not allowed!
- Single quotes not allowed!
- Backspaces not allowed!
- Commas at the end of lists not allowed.

json.loads *does *accept this, in the body text of an @data ftp node:

[
["user-name", "host-name", "password"],
["C:/leo.repo/leo-editor/README.MD"],
["C:/leo.repo/leo-editor/INSTALL.TXT"]
]

As shown, the first sub-list describes the server.  All other sub-lists 
describe files to be uploaded.  The present code requires items of the form:

[path, time1]

or

[path, time1, time2]

Imo, a bare path should also be allowed:

   [path]

The idea is that the file will be written unless its modification time 
matches time time2, with time2 defaulting to -1.  Perhaps should be changed.

That's what I have so far.

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 from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rev 79ba3d: potential crasher in refresh-from-disk

[vitalije]

@Edward, I have noticed that this crasher is still present in several 
branches. I don't know if it will be removed once those branches are merged 
with master. I suppose it will. But watch out that its presence is not 
affecting work on other branches.

Vitalije

-- 
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, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: leo ftp

[Edward K. Ream]

On Mon, Jul 10, 2017 at 12:01 PM, Ivanov Dmitry  wrote:

> > ​I'll see what I can do today.  It looks like this plugin needs some
> work.
>
> As far as I remember it needs ftp credentials written in JSON format.
> Maybe, user did something wrong with JSON format? I'll look as well.
>

​I'm working on clarifying the code, but the real need is a proper
docstring, telling especially what the json should contain, with examples.

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 from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Vote: display trailing whitespace by default?

[Edward K. Ream]

On Mon, Jul 10, 2017 at 9:45 AM, Terry Brown  wrote:

> Hi - I've added a syntax highlighting rule to Leo to display trailing
> whitespace, which is the default in some editors, nano for example.
>
> The trailing whitespace is shown underlined with small red dots,
> although you can change the color.
>
> So what's the consensus - have this turned on by default, or not?
>

​I vote for this to be the default.  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 from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Vote: display trailing whitespace by default?

[Kent Tenney]

same (I voted yes on the poll)

On Mon, Jul 10, 2017 at 10:32 AM, vitalije  wrote:

> +1 for displaying by default
>
>
> On Monday, July 10, 2017 at 4:45:39 PM UTC+2, Terry Brown wrote:
>>
>> Hi - I've added a syntax highlighting rule to Leo to display trailing
>> whitespace, which is the default in some editors, nano for example.
>>
>> The trailing whitespace is shown underlined with small red dots,
>> although you can change the color.
>>
>> So what's the consensus - have this turned on by default, or not?
>>
>> We can discuss in this list, but if you just want to vote yes or no,
>> here's a poll:
>>
>> https://docs.google.com/forms/d/1xrrUYTNcfK6Fvu3_HTEkmzF1O7p
>> PscGwWs9oFxg2Bv0
>>
>> Cheers -Terry
>>
> --
> 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, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Vote: display trailing whitespace by default?

[vitalije]

+1 for displaying by default

On Monday, July 10, 2017 at 4:45:39 PM UTC+2, Terry Brown wrote:
>
> Hi - I've added a syntax highlighting rule to Leo to display trailing 
> whitespace, which is the default in some editors, nano for example. 
>
> The trailing whitespace is shown underlined with small red dots, 
> although you can change the color. 
>
> So what's the consensus - have this turned on by default, or not? 
>
> We can discuss in this list, but if you just want to vote yes or no, 
> here's a poll: 
>
>
> https://docs.google.com/forms/d/1xrrUYTNcfK6Fvu3_HTEkmzF1O7pPscGwWs9oFxg2Bv0 
>
> Cheers -Terry 
>

-- 
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, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: A road to branch pollution: git stash goes back in time

[Edward K. Ream]

On Sunday, July 9, 2017 at 1:09:57 AM UTC-5, Edward K. Ream wrote:

*Danger*: *stashing goes back in time in master*. All of Leo's caches must 
> be completely cleared!
>

And I just came across another danger.  If I have written a file in master, 
I have also written it to *master's* cache.  Doing git branch -b doesn't 
clear that cache.

As a result, on several occasions I have gotten this:
Internal Leo error in checkForChangedNodes

A workaround is to clear the cache for the affected .leo file.  Not sure 
what the real solution is.

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 from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: commands to move to next file in 'file edit list'?

[lewis]

Heh, just discovered this mouse method.

Hover over a tab, and mouse wheel up/down to traverse the list of open Leo 
files.

Regards
Lewis

-- 
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, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Vote: display trailing whitespace by default?

[Terry Brown]

Hi - I've added a syntax highlighting rule to Leo to display trailing
whitespace, which is the default in some editors, nano for example.

The trailing whitespace is shown underlined with small red dots,
although you can change the color.

So what's the consensus - have this turned on by default, or not?

We can discuss in this list, but if you just want to vote yes or no,
here's a poll:

https://docs.google.com/forms/d/1xrrUYTNcfK6Fvu3_HTEkmzF1O7pPscGwWs9oFxg2Bv0

Cheers -Terry

-- 
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, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: leo ftp

[Edward K. Ream]

On Sun, Jul 9, 2017 at 11:33 PM, zhaohe wang  wrote:

> ValueError: No JSON object could be decoded
> Would you teach me how to use this plugin?
>

​I'll see what I can do today.  It looks like this plugin needs some work.

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 from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: How does instant update work in Pharo?

[Edward K. Ream]

On Mon, Jul 10, 2017 at 12:00 AM, Xavier G. Domingo 
wrote:

​
>> I'm already noticing the constraints more.  I want full reload
yesterday, and I would like to explore Python patterns that would allow
arbitrary Python apps to reload themselves.​
 ​

​
​
> Today I've had a fool idea about this: to change one object into its new
"version" you need just... its diff! Maybe that could be leveraged to make
the new version of the object by applying the diff (patch) to it?​

I appreciate your enthusiasm, but this is unlikely to work.

​> ​
have you considered asking how would the experts do that at the Python-list
?

​​
​Not really.  I've looked at the Pharo sources. I doubt if they contains
are any wonder-ideas that we can use.​
​ The important thing is the goal.  We have to adapt that goal to our
world.​


​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 from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Aha: outline-oriented git diffs are straightforward

[Edward K. Ream]

On Sunday, July 9, 2017 at 7:39:14 PM UTC-5, Edward K. Ream wrote:

> The Aha: use git...*only *to deliver *complete *old files.

#501 

 
now contains prototype code using git show to deliver a complete file.

I won't discuss the usual programming details here. See #501 if you are 
interested.

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 from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.