Re: @nosent and file parsing

I created a github 'issue' I don't see a way to classify it as 'wishlist' On Wed, Mar 4, 2015 at 9:08 AM, Edward K. Ream edream...@gmail.com wrote: On Thu, Feb 19, 2015 at 9:59 AM, Kent Tenney kten...@gmail.com wrote: might it be feasible / make sense to offer @auto style parsing when doing

Re: @nosent and file parsing

On Thu, Feb 19, 2015 at 9:59 AM, Kent Tenney kten...@gmail.com wrote: might it be feasible / make sense to offer @auto style parsing when doing @nosent 'refresh from disk' into a blank body? IE: initial import ​Please file a wishlist bug item for this. Edward -- You received this message

Re: @nosent and file parsing

might it be feasible / make sense to offer @auto style parsing when doing @nosent 'refresh from disk' into a blank body? IE: initial import Thanks, Kent On Wed, Feb 18, 2015 at 7:03 AM, Edward K. Ream edream...@gmail.com wrote: On Wed, Feb 18, 2015 at 6:45 AM, Kent Tenney kten...@gmail.com

Re: @nosent and file parsing

Perhaps user-configurable, with a @bool auto-on-refresh-nosent = True? On 2/19/2015 10:59 AM, Kent Tenney wrote: might it be feasible / make sense to offer @auto style parsing when doing @nosent 'refresh from disk' into a blank body? IE: initial import Thanks, Kent On Wed, Feb 18, 2015 at 7:03

Re: @nosent and file parsing

Feels like beating a dead horse here, but +1 for this. --Jake On 2/19/2015 10:59 AM, Kent Tenney wrote: might it be feasible / make sense to offer @auto style parsing when doing @nosent 'refresh from disk' into a blank body? IE: initial import Thanks, Kent On Wed, Feb 18, 2015 at 7:03 AM,

@nosent and file parsing

I'm seeing that @nosent file.py doesn't create nodes for function definitions I seem to remember that it did, am I mistaken? Thanks, Kent Leo 5.0-final, build 20150127110559, Tue, Jan 27, 2015 11:05:59 AM Git repo info: branch = master, commit = 823c0c8faf06 -- You received this message

Re: @nosent and file parsing

On Wed, Feb 18, 2015 at 6:45 AM, Kent Tenney kten...@gmail.com wrote: OK, I think I see. I'm expecting the capability of @auto, which is more automatic ... I'm used to rclick refresh parsing on import, @nosent requires parsing manually, creating the required nodes. ​Exactly. Note that

Re: @nosent and file parsing

OK, I think I see. I'm expecting the capability of @auto, which is more automatic ... I'm used to rclick refresh parsing on import, @nosent requires parsing manually, creating the required nodes. This is about sorting out the @xxx landscape. I would hope the simple automation of @auto could