Sorry for flooding,

two more comments

– the page actually says
  “broken links in this section indicate that install package is not yet
available”
  so yes, this is expected behaviour
– I just said 'vimperator' which I used to have,
  now it’s Tridactyl instead

Am 02.02.21 um 18:23 schrieb Hauke Rehr:
> Just in order to not have you worry about it:
> it’s been a trailing /
> Usually, I go one level up by 'gu' using vimperator,
> but this time it didn’t work and I deleted the
> trailing part of the URL manually
> … and didn’t delete enough
> 
> So yes, /J903 works.
> 
> Am 02.02.21 um 18:13 schrieb Hauke Rehr:
>> Sorry, I’ve been wrong.
>> It didn’t work on its own but clicking the link
>> (which I overlooked) actually got me to J903
>> … strange
>> But that page doesn’t point to a subordinate AIOx page.
>>
>> Am 02.02.21 um 18:11 schrieb Hauke Rehr:
>>> Even J903/ doesn’t exist, let alone any child node.
>>> https://code.jsoftware.com/wiki/System/Installation
>>> doesn’t point to any 903 nodes.
>>>
>>> So where does your URL come from?
>>>
>>> Am 02.02.21 um 18:04 schrieb Devon McCormick:
>>>> Am I the only one who gets a blank page when I try to load (Windows) 9.03
>>>> by clicking on 
>>>> https://code.jsoftware.com/wiki/System/Installation/J903/AIOx
>>>> ?
>>>>
>>>> On Tue, Feb 2, 2021 at 10:33 AM Henry Rich <[email protected]> wrote:
>>>>
>>>>> I am not going to enlarge my commit messages.  They need to be short.
>>>>>
>>>>> Any explanation should be in commentary in the code, for maximum benefit.
>>>>>
>>>>> I agree that a new generation of developers is needed.  Perhaps they're
>>>>> out there already - many people seem to build JE from the source.
>>>>>
>>>>> It's a complex codebase, through.  Why don't you dive in by adding
>>>>> commentary to some of the parts that lack it?  You would learn something
>>>>> of the code without the risk of breaking anything, and you would
>>>>> definitely be making things easier for the next guy.  I would review
>>>>> anything you write.
>>>>>
>>>>> Henry Rich
>>>>>
>>>>>
>>>>>
>>>>> On 2/1/2021 11:25 PM, ethiejiesa via Programming wrote:
>>>>>> Raul Miller <[email protected]> wrote:
>>>>>>> https://github.com/jsoftware/jsource/commits/master might interest
>>>>> you...
>>>>>> Indeed, I have the repo cloned locally!
>>>>>>
>>>>>> However, when digging through old bug reports, I find it quite
>>>>> challenging to
>>>>>> match up the "fixed" notices with the corresponding code commits. In
>>>>> cases with
>>>>>> a clear test case demonstrating the bug, we can use git-bisect to sleuth
>>>>> out
>>>>>> the commit that eliminates the failure. However, cases without this
>>>>> almost
>>>>>> invariably defeat my investigative skills.
>>>>>>
>>>>>> For posterity's sake, and if it's not too much of a hassle, I thought it
>>>>> might
>>>>>> be helpful to have some commits/diffs/comments attached to those "fixed"
>>>>>> messages.
>>>>>>
>>>>>> I will admit to a bit of an ulterior motive here, though.
>>>>>>
>>>>>> Bill, Eric, and Henry have deep domain knowledge about JE. I am
>>>>> personally
>>>>>> hoping that sharing the diffs would also spark discussion and give a
>>>>> natural
>>>>>> avenue to share and spread such expertise.
>>>>>>
>>>>>> The gory details are exceptionally interesting!
>>>>>>
>>>>>>
>>>>>> Permit me to query a broader point, though.
>>>>>>
>>>>>> It strikes me that the git-shortlog on the repo is very short:
>>>>>>
>>>>>>      $ git shortlog --summary
>>>>>>      6        Chris Burke
>>>>>>      231      Eric Iverson
>>>>>>      1430     HenryHRich
>>>>>>      1        bill
>>>>>>      597      bill lam
>>>>>>      3        cdb
>>>>>>      3        kbi
>>>>>>
>>>>>> For the most part, we only have 3 devs, with all of them part of the old
>>>>> guard,
>>>>>> per se. Better yet, Henry has authored over 62% of all commits! Granted,
>>>>> this
>>>>>> only reflects the history from 2016 onward, but my question is this: Do
>>>>> we have
>>>>>> up and coming JE hackers that can pick up the torch when the time comes?
>>>>>>
>>>>>>
>>>>>> Anyway, maybe JSoftware has a vision for the future that I've failed to
>>>>> pick up
>>>>>> on. The ulterior motive behind my "share a bit about the fix" is to
>>>>> perhaps
>>>>>> open a channel with the community that sucks in potential JE devs like
>>>>> myself!
>>>>>> I was just trying to be sneaky about things by suggesting something very
>>>>> simple
>>>>>> and, hopefully, hassle-free.
>>>>>>
>>>>>>
>>>>>> 2!:55
>>>>>> ----------------------------------------------------------------------
>>>>>> For information about J forums see http://www.jsoftware.com/forums.htm
>>>>>
>>>>>
>>>>> --
>>>>> This email has been checked for viruses by AVG.
>>>>> https://www.avg.com
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> For information about J forums see http://www.jsoftware.com/forums.htm
>>>>>
>>>>
>>>>
>>>
>>
> 

-- 
----------------------
mail written using NEO
neo-layout.org

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to