Re: run pylint in leo-editor UnicodeDecodeError

2016-10-16 Thread zhaohe wang
Would you tell me which line like plain ascii?
error == [], when I run your script both wiht pylint-leo-rc.txt and my py 
file.

在 2016年10月16日星期日 UTC+8上午9:10:38,Edward K. Ream写道:
>
>
> On Fri, Oct 14, 2016 at 6:16 AM, zhaohe wang > > wrote:
>>
>>> Leo 5.4-devel, build 20160722143100, Fri, Jul 22, 2016  2:31:00 PM
>>> Git repo info: branch = master, commit = cb40bc3b4ca7
>>> Python 2.7.12, PyQt version 4.8.7
>>> linux2
>>> pylint: keyLog.py
>>> Traceback (most recent call last):
>>>
>>
>>   File 
>>> "/usr/local/lib/python2.7/dist-packages/backports/configparser/__init__.py",
>>>  
>>> line 1101, in _read
>>> raise MissingSectionHeaderError(fpname, lineno, line)
>>> backports.configparser.MissingSectionHeaderError: File contains no 
>>> section headers.
>>> file: '/home/swot/leo-editor/leo/test/pylint-leo-rc.txt', line: 1
>>> u'@first # -*- coding: utf-8 -*-\n'
>>> pylint: done  0.23 sec.
>>>
>>
>> ​Not sure what is happening.  You might try removing non-ascii characters 
>> from the file.
>>
>  
> The same kind of thing happened to me today after upgrading my Python 
> distribution.
>  
> To find the location of the problem, I wrote this script:
>
> path = r'c:\leo.repo\leo-editor\leo\test\pylint-leo-rc.txt'
> f = open(path)
> s = f.read()
> f.close()
> print(len(s))
> errors = []
> n = 0
> for i, line in enumerate(g.splitLines(s)):
> try:
> print('  %3s %4s %s' % (i+1, n, line.rstrip()))
> except UnicodeEncodeError:
> print('**%3s %4s %s' % (i+1, n, len(line.rstrip(
> errors.append(i)
> n += len(line)
> print('error lines: %s' % errors)
>
> The line *looked* like plain ascii, but removing it solved the problem.  
> This was a strange one.
>
> 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.


Proposal: remove commit_timestamp.json

2016-10-16 Thread Edward K. Ream
At present, leoVersion.py gets version info by parsing 
leo/core/commit_timestamp.json. There are at least two unacceptable 
problems with this approach:

1. The dates don't get updated if a developer (like me!) forgets to install 
the git hooks.

Just today I noticed that the last update was supposedly in July!

2. Continually changing commit_timestamp.json creates merge conflicts.

There is a much easier way. Rather than parsing commit_timestamp.json, we 
can get info about the last commit from  "git log -1". Like this:

p = subprocess.Popen(
["git", "log" , '-1', '--date=default-local'],
stdout=subprocess.PIPE,
shell=True,
)
out, err = p.communicate()
out = g.toUnicode(out)
m = re.search('commit (.*)\n', out)
commit = m.group(1)[0:8].strip() if m else ''
m = re.search('Date: (.*)\n', out)
date = m.group(1).strip() if m else '

This works well in my tests.

For official releases, we expect that git won't be installed, or that "git 
log" will fail because the official release contains no .git directory.  
Either way, the code will catch exceptions thrown by subprocess and return 
the official (static) release date defined in leoVersion.py.

My release testing will ensure that this approach works.  Do you see any 
problems with 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.


Please hold all commits until Leo 5.4b1 goes out the door

2016-10-16 Thread Edward K. Ream
Expect b1 to be released later today.  There is lots of testing involved, 
which I would have to redo if I pulled any changes.

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: Proposal: remove commit_timestamp.json

2016-10-16 Thread Edward K. Ream
On Sunday, October 16, 2016 at 11:18:02 AM UTC-5, Edward K. Ream wrote:

p = subprocess.Popen(
> ["git", "log" , '-1', '--date=default-local'],
> stdout=subprocess.PIPE,
> shell=True)
>

Testing on Linux shows that the shell argument should be set as follows:

shell=sys.platform.startswith('win'),

EKR

-- 
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: Proposal: remove commit_timestamp.json

2016-10-16 Thread Edward K. Ream
On Sunday, October 16, 2016 at 11:50:00 AM UTC-5, Edward K. Ream wrote:
>
> On Sunday, October 16, 2016 at 11:18:02 AM UTC-5, Edward K. Ream wrote:
>
> p = subprocess.Popen(
>> ["git", "log" , '-1', '--date=default-local'],
>> stdout=subprocess.PIPE,
>> shell=True)
>>
>
When this code is run outside a git repo, git log will issue a "fatal" 
error. This will typically be true when the user is running an "official" 
release. We can suppress such irrelevant messages by adding this arg to the 
call to subprocess.Popen:

stderr=None if trace else subprocess.DEVNULL,

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: run pylint in leo-editor UnicodeDecodeError

2016-10-16 Thread Edward K. Ream
On Sunday, October 16, 2016 at 10:16:04 AM UTC-5, zhaohe wang wrote:

Would you tell me which line like plain ascii?
> error == [], when I run your script both wiht pylint-leo-rc.txt and my py 
> file.
>

Hmm.  It looks like all the lines of these two files are ascii.  So it's 
even more of a mystery why you are getting Unicode errors.

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: Proposal: remove commit_timestamp.json

2016-10-16 Thread 'Terry Brown' via leo-editor
On Sun, 16 Oct 2016 09:18:02 -0700 (PDT)
"Edward K. Ream"  wrote:

> At present, leoVersion.py gets version info by parsing 
> leo/core/commit_timestamp.json. There are at least two unacceptable 
> problems with this approach:
> 
> 1. The dates don't get updated if a developer (like me!) forgets to
> install the git hooks.
> 
> Just today I noticed that the last update was supposedly in July!

Heh, I don't think it's the end of the world if this happens, I guess
we / I could set up some sort of monitoring for that case, but just
noticing it (eventually) and installing the hooks works too.

> 2. Continually changing commit_timestamp.json creates merge conflicts.

Which can be resolved with 

  git checkout --ours leo/core/commit_timestamp.json

(seeing it's not that critical which one you use).

Certainly in a git repo. commit_timestamp.json isn't needed.
The point of it was to give useful, *fine grained* version ID in non-git
contexts. I think "you have to use git to use Leo" in an unreasonable
barrier, seeing not all Leo users are coders and therefore may never
use a VCS, and I usually point people to 
https://github.com/leo-editor/leo-editor/archive/master.zip
to get the current Leo.  There's no git repo. in that .zip.
O
fficial releases don't offer fine grained version info., the first
thing we'd tell someone with a problem to try is running the latest
code, and if they're getting it from master.zip, commit_timestamp.json
is useful.

So I'd argue for leaving commit_timestamp.json as is and living with
the two shortcomings you identified.  But if it's not bearable, we can
do something like you suggest.

> There is a much easier way. Rather than parsing
> commit_timestamp.json, we can get info about the last commit from
> "git log -1". Like this:
> 
> p = subprocess.Popen(
> ["git", "log" , '-1', '--date=default-local'],
> stdout=subprocess.PIPE,
> shell=True,
> )
> out, err = p.communicate()
> out = g.toUnicode(out)
> m = re.search('commit (.*)\n', out)
> commit = m.group(1)[0:8].strip() if m else ''
> m = re.search('Date: (.*)\n', out)
> date = m.group(1).strip() if m else '
> 
> This works well in my tests.
> 
> For official releases, we expect that git won't be installed, or that
> "git log" will fail because the official release contains no .git
> directory. Either way, the code will catch exceptions thrown by
> subprocess and return the official (static) release date defined in
> leoVersion.py.
> 
> My release testing will ensure that this approach works.  Do you see
> any problems with 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: Proposal: remove commit_timestamp.json

2016-10-16 Thread Edward K. Ream
On Sun, Oct 16, 2016 at 4:08 PM, 'Terry Brown' via leo-editor

So I'd argue for leaving commit_timestamp.json as is and living with
> the two shortcomings you identified.  But if it's not bearable, we can
> do something like you suggest.
>

​I've already done what I suggested, and it works fine, especially for
official releases. But I see your point: the daily builds won't have
detailed version info.

Most importantly, I want to make things solid for us core developers, and
for those that get Leo using git. Having to install hooks is intolerable in
the long run. The new way is far better.

What to do about daily snapshots? Maybe the script that creates the
snapshot could create commit_timestamp.json. In this case, leoVersion.py
would fall back on the legacy code if git is not around.  It would be
straightforward to do this.

I like this approach--it doesn't let the tail wag the dog. What do you
think? For sure I am not going back to the old way.

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: Proposal: remove commit_timestamp.json

2016-10-16 Thread Edward K. Ream
On Sunday, October 16, 2016 at 1:15:56 PM UTC-5, Edward K. Ream wrote:

When this code is run outside a git repo, git log will issue a "fatal" 
> [sic] error. This will typically be true when the user is running an 
> "official" release. We can suppress such irrelevant messages by adding this 
> arg to the call to subprocess.Popen:
>
> stderr=None if trace else subprocess.DEVNULL,
>

Arrgh.  pylint informs me that DEVNULL does not exist with Python2. Using 
subprocess.PIPE works with both 2 and 3.

EKR

-- 
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: Proposal: remove commit_timestamp.json

2016-10-16 Thread Edward K. Ream
On Sun, Oct 16, 2016 at 5:13 PM, Edward K. Ream  wrote:

But I see your point: the daily builds won't have detailed version info.
>
​[snip]​


> What to do about daily snapshots? Maybe the script that creates the
> snapshot could create commit_timestamp.json.
>

​Heh.  The zip file's name contains the commit hash, so the user can find
out the exact version. Isn't that enough? I don't want write any more code
to deal with this issue.

EKR

-- 
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: Proposal: remove commit_timestamp.json

2016-10-16 Thread Mike Hodson
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?
I mean I must be missing something horribly wrong if I'm going to the
same URL posted by Terry and getting something without a hash.

That said, I did more digging. Seems that the full hash is contained
-as a comment- in the zip file...
With >2000 files in the zip file, infozip at the commandline shows the
comment -at the top- and in 1 second flat my screen goes from me
hitting enter on 'unzip master.zip' and seeing the end of the files
spit out verbosely and my prompt again.

So for future reference: If you link the redirectable "master.zip"
link, the hash _does not appear_ to be contained in the filename, but
_is_ contained in the Comment.
Maybe I should send a bug/feature request up the Infozip pipeline to
put comments "after" the verbose extracted files...

Thanks,

Mike

-- 
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: run pylint in leo-editor UnicodeDecodeError

2016-10-16 Thread zhaohe wang



Found it !!!
Line 207 in pylint-leo-rc-ref.txt
You committed on 29 Feb.


I changed the test py codes below. Add codecs.utf_8_decode(line), please 
have a ref
@language python
@tabwidth -4

import codecs

# path = r'c:\leo.repo\leo-editor\leo\test\pylint-leo-rc.txt'
path = r'/home/swot/leo-editor/leo/test/pylint-leo-rc.txt'
# path = r'/home/swot/app/keyLog.py'

f = open(path)
s = f.read()
f.close()
print(len(s))
errors = []
n = 0
for i, line in enumerate(g.splitLines(s)):
try:
print('  %3s %4s %s' % (i+1, n, line.rstrip()))
codecs.utf_8_decode(line)
except UnicodeEncodeError:
print('**%3s %4s %s' % (i+1, n, len(line.rstrip(
errors.append(i)
n += len(line)
print('error lines: %s' % errors)

在 2016年10月17日星期一 UTC+8上午12:56:44,Edward K. Ream写道:
>
> On Sunday, October 16, 2016 at 10:16:04 AM UTC-5, zhaohe wang wrote:
>
> Would you tell me which line like plain ascii?
>> error == [], when I run your script both wiht pylint-leo-rc.txt and my py 
>> file.
>>
>
> Hmm.  It looks like all the lines of these two files are ascii.  So it's 
> even more of a mystery why you are getting Unicode errors.
>
> 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: Proposal: remove commit_timestamp.json

2016-10-16 Thread 'Terry Brown' via leo-editor
On Sun, 16 Oct 2016 20:12:26 -0500
"Edward K. Ream"  wrote:

> On Sun, Oct 16, 2016 at 7:49 PM, Mike Hodson 
> wrote:
> 
> > On Sun, Oct 16, 2016 at 4:24 PM, Edward K. Ream
> >  wrote:  
> > > The zip file's name contains the commit hash, so the user can
> > > find out  
> > the
> > ​ ​
> > exact version.
> >
> > Where exactly am I supposed to be looking that I'm unable to find
> > this version/commit of the master?
> >  
> 
> ​Here's an example.  I downloaded
> leo-editor-281522323a89c27b7c58338b1eaa624cbd383078.zip
> from two days ago.

The obvious non-git link is
https://github.com/leo-editor/leo-editor/archive/master.zip ('Latest' at 
http://leoeditor.com/download.html), which has no hash, as Mike said.

> Using gitk, ​
> 
> ​I found the Sha1 hash​ for this commit:
> 
> Author: Edward K. Ream   2016-10-14 16:13:27
> [snip]
> 
> Updated the 5.4 docs from my "to be documented" mailbox.
> 
> Yes, the user must have git installed to get this information, so the
> hash isn't all that useful.  Otoh, if there were a problem with
> the .zip file, one of Leo's devs could recover any necessary info.
> 
> Put another way, the best, easiest way to get any version of Leo is
> to use git.  Any other way is less convenient.

This is still the "should using git be a requirement for using Leo"?
question.  Without some non-git source of version info., non-git users
have no easy way of downloading a known version, other than official
releases, which is almost certainly not helpful if they're reporting a
problem and we're trying to fix it.

There is no script that makes these files any more, they're just
supplied automagically by GitHub.

But hah - a possible, partial,  solution.  Instead of this link:
https://github.com/leo-editor/leo-editor/archive/master.zip
we could use this:
https://github.com/leo-editor/leo-editor/archive/master@%7B0%20day%20ago%7D.zip
i.e.
https://github.com/leo-editor/leo-editor/archive/master@{0 day ago}.zip
which downloads the latest commit, *with the hash included*, in the file name.

It's still somewhat less convenient for the non-git user, seeing
the .zip unpacks to a different folder every time you download it (and
there's a new revision, of course).  People just wanting a link they can
grab and unzip to stay current can still use
https://github.com/leo-editor/leo-editor/archive/master.zip of course,
sans useful versioning information.

Also, reporting version info. in the log will be less robust.  You have
to rely on people not renaming the directory, so you can parse the
version out of sys.argv[0] or whatever.  But surely no one would rename
a directly called
leo-editor-4373f88f0dd9b25daa22e0b31f2f23acf88fe3fe ;-)

I think we're getting rid of a couple of minor (well, ok, one-time
medium in the case of installing the hooks) inconveniences for Leo
devs., at the cost of the most robust and frictionless way to get
accurate versioning info. from users reporting problems.

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: Proposal: remove commit_timestamp.json

2016-10-16 Thread Mike Hodson
On Sun, Oct 16, 2016 at 4:24 PM, Edward K. Ream  wrote:
> The zip file's name contains the commit hash, so the user can find out the
> exact version. Isn't that enough? I don't want write any more code to deal
> with this issue.
>

I just tried downloading the master.zip from github; the only version
info I see is that this is supposed to be "5.4-b1" inside of
PKG-INFO.TXT.

Checking the actual 'master' on github shows that leoApp.py was the
latest modified file, and yes indeed, this is in the zip(after
extracting):
-rw-r--r-- 1 mike users 148K Oct 16 16:34 ./leo/core/leoApp.py

The current git hash is e09c486741b587508314dddff90bfc368c3af8f0
Searching for both the beginning, and end, (as I'm really not sure
what the 'short' hashes are, either the beginning or end..)


mike@odin ~/leo-editor-master $ grep -r 3af8f0 *
mike@odin ~/leo-editor-master $ grep -r e09c48 *
mike@odin ~/leo-editor-master $

Where exactly am I supposed to be looking that I'm unable to find this
version/commit of the master?

Or do I misunderstand?

Thanks,

Mike

-- 
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: Proposal: remove commit_timestamp.json

2016-10-16 Thread Edward K. Ream
On Sun, Oct 16, 2016 at 7:49 PM, Mike Hodson  wrote:

> On Sun, Oct 16, 2016 at 4:24 PM, Edward K. Ream 
> wrote:
> > The zip file's name contains the commit hash, so the user can find out
> the
> ​ ​
> exact version.
>
> Where exactly am I supposed to be looking that I'm unable to find this
> version/commit of the master?
>

​Here's an example.  I downloaded
leo-editor-281522323a89c27b7c58338b1eaa624cbd383078.zip
from two days ago.

Using gitk, ​

​I found the Sha1 hash​ for this commit:

Author: Edward K. Ream   2016-10-14 16:13:27
[snip]

Updated the 5.4 docs from my "to be documented" mailbox.

Yes, the user must have git installed to get this information, so the hash
isn't all that useful.  Otoh, if there were a problem with the .zip file,
one of Leo's devs could recover any necessary info.

Put another way, the best, easiest way to get any version of Leo is to use
git.  Any other way is less convenient.

EKR

-- 
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: Proposal: remove commit_timestamp.json

2016-10-16 Thread Mike Hodson
And, there is no hash in the filename. The filename it downloads is
either "master" "master.zip" or "leo-editor-master.zip" depending on
Chrome, Curl, or Wget naming the file (and/or after following the
redirect manually with curl)

Thanks,

Mike




On Sun, Oct 16, 2016 at 6:49 PM, Mike Hodson  wrote:
> On Sun, Oct 16, 2016 at 4:24 PM, Edward K. Ream  wrote:
>> The zip file's name contains the commit hash, so the user can find out the
>> exact version. Isn't that enough? I don't want write any more code to deal
>> with this issue.
>>
>
> I just tried downloading the master.zip from github; the only version
> info I see is that this is supposed to be "5.4-b1" inside of
> PKG-INFO.TXT.
>
> Checking the actual 'master' on github shows that leoApp.py was the
> latest modified file, and yes indeed, this is in the zip(after
> extracting):
> -rw-r--r-- 1 mike users 148K Oct 16 16:34 ./leo/core/leoApp.py
>
> The current git hash is e09c486741b587508314dddff90bfc368c3af8f0
> Searching for both the beginning, and end, (as I'm really not sure
> what the 'short' hashes are, either the beginning or end..)
>
>
> mike@odin ~/leo-editor-master $ grep -r 3af8f0 *
> mike@odin ~/leo-editor-master $ grep -r e09c48 *
> mike@odin ~/leo-editor-master $
>
> Where exactly am I supposed to be looking that I'm unable to find this
> version/commit of the master?
>
> Or do I misunderstand?
>
> Thanks,
>
> Mike

-- 
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: Proposal: remove commit_timestamp.json

2016-10-16 Thread 'Terry Brown' via leo-editor
On Sun, 16 Oct 2016 19:20:23 -0600
Mike Hodson  wrote:

> That said, I did more digging. Seems that the full hash is contained
> -as a comment- in the zip file...
> With >2000 files in the zip file, infozip at the commandline shows the
> comment -at the top- and in 1 second flat my screen goes from me
> hitting enter on 'unzip master.zip' and seeing the end of the files
> spit out verbosely and my prompt again.

Heh, well spotted, seems GitHub puts the hash in the .zip as a comment.

But I don't think that helps us, seeing there's no obvious way to know
where the user stored the .zip, which you'd need to know to access this
info.

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.