Re: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
On Mon, Oct 17, 2016 at 3:51 AM, Edward K. Ream wrote: > ​​ > > When I awoke early this morning, I saw the way forward. It should satisfy > everybody: > ​[snip]​ 2. Create leo/core/ > ​​ > commit_timestamp.json in @button make-leo in leoDist.leo. > ​The create_json

Re: run pylint in leo-editor UnicodeDecodeError

2016-10-17 Thread Edward K. Ream
On Sun, Oct 16, 2016 at 8:41 PM, zhaohe wang wrote: > > > Found it !!! > ​​ > Line 207 in pylint-leo-rc-ref.txt > You

Re: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
​​ On Mon, Oct 17, 2016 at 3:51 AM, Edward K. Ream wrote: ​When I awoke early this morning, I saw the way forward. It should satisfy > everybody: > ​Rev 4c953099 puts the new scheme in place. It seems to work well. There is now no need for any git hooks. You can

Re: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
​​ On Sun, Oct 16, 2016 at 8:20 PM, Mike Hodson wrote: On Sun, Oct 16, 2016 at 7:12 PM, Edward K. Ream wrote: > > Here's an example. I downloaded > > leo-editor-281522323a89c27b7c58338b1eaa624cbd383078.zip > > from two days ago. > > How? > ​From the two

Re: Fw: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
On Mon, Oct 17, 2016 at 11:57 AM, Jacob Peck wrote: > I'm with Terry on this -- the commit_timestamp.json file has been > immensely helpful in debugging user issues in the past. Relegating the > commit hash to some funky filename is not an acceptable option. > ​Ok. I can

Re: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
On Mon, Oct 17, 2016 at 5:17 AM, Edward K. Ream wrote: ​Rev 4c953099 puts the new scheme in place. It seems to work well. There is now no need for any git hooks. You can disable them if you like, but they won't interfere with anything if they exist. ​The format of

Re: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
On Monday, October 17, 2016 at 5:24:23 AM UTC-5, Edward K. Ream wrote: ​Rev 4c953099 puts the new scheme in place. It seems to work well. > > There is now no need for any git hooks. You can disable them if you like, > but they won't interfere with anything if they exist. > > ​The format of

LeoDocs - User Guide update mod_http.py

2016-10-17 Thread lewis
LeoDocs - User Guide update request: The mod_http plugin docstring refers to "Viewing loaded outlines in a browser, e.g. at http://localhost:8130/ " LeoDocs.leo at Leo's Documentation-->Users Guide-->Plugins-->@rst html\plugins.html-->Gui-independent plugins-->Servers-->mod_http.py 2. Start a

Re: Proposal: remove commit_timestamp.json

2016-10-17 Thread 'Terry Brown' via leo-editor
From: Edward K. Ream To: leo-editor Sent: Monday, October 17, 2016 3:51 AM Subject: Re: Proposal: remove commit_timestamp.json ​​On Sun, Oct 16, 2016 at 8:20 PM, Mike Hodson wrote: On Sun, Oct 16, 2016 at 7:12

Devs: please delete your git hooks

2016-10-17 Thread Edward K. Ream
These are the commit-msg and pre-commit files in leo-editor/.git/hooks. They won't do any harm, or even be all that inconvenient, but they serve no purpose now. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this

Re: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
On Monday, October 17, 2016 at 11:23:08 AM UTC-5, Edward K. Ream wrote: > To recap, the new scheme is *much *better than the old because: That summary, while true, doesn't get to the heart of the matter. And it's repetitious. In fact, we need commit_timestamp.json only at the *exact instant*

Fw: Proposal: remove commit_timestamp.json

2016-10-17 Thread 'Terry Brown' via leo-editor
[meant to post to the list, not just Edward] From: Edward K. Ream To: leo-editor Cc: terry_n_br...@yahoo.com Sent: Monday, October 17, 2016 11:23 AM Subject: Re: Proposal: remove commit_timestamp.json On Monday, October 17, 2016 at

Re: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
On Monday, October 17, 2016 at 9:04:52 AM UTC-5, Terry Brown wrote: I'm not really sure this has any utility :-/ > I am about to release Leo 5.4b1. Imo, the new scheme works very well. Leo *always* reports first 8 characters of the git hash and git date, even when there is no git around, which

Re: Fw: Proposal: remove commit_timestamp.json

2016-10-17 Thread Jacob Peck
I'm with Terry on this -- the commit_timestamp.json file has been immensely helpful in debugging user issues in the past. Relegating the commit hash to some funky filename is not an acceptable option. Git hooks are painless. Why is this suddenly an issue? -->Jake On 10/17/2016 12:50 PM,

Re: Fw: Proposal: remove commit_timestamp.json

2016-10-17 Thread 'Terry Brown' via leo-editor
From: Edward K. Ream To: leo-editor Sent: Monday, October 17, 2016 1:40 PM Subject: Re: Fw: Proposal: remove commit_timestamp.json On Mon, Oct 17, 2016 at 11:57 AM, Jacob Peck wrote: I'm with Terry on

Re: Fw: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
On Mon, Oct 17, 2016 at 11:57 AM, Jacob Peck wrote: ​> ​ Why is this suddenly an issue? ​A better answer is that I have been working on distribution for the last three days. Problems come up in that context that we completely ignore normally. Let's be clear. The new