User talk:Thundergnat: Difference between revisions

From Rosetta Code
Content added Content deleted
(→‎Heronian triangles: new section)
 
(253 intermediate revisions by 22 users not shown)
Line 1: Line 1:
[[User_talk:Thundergnat/archive|Archive of older talk page entries]]
Hi. Nice job on the Perl6 version of [[Write language name in 3D ASCII]] ! :-)
--[[User:Grondilu|Grondilu]] 19:36, 14 November 2012 (UTC)


Hi Thundergnat.


==Syntax highlighting disappearing after a certain point for some tasks==
Regarding the Perl 6 solution of the checking Machin Style formulas.
The problem is that the Perl 6 solution uses floating point numbers.
The task requires one to use exact computations.


Take the [[List comprehensions]] task for example. It's fine up to and including the Swift entry but then disappears from Tcl onwards even though Tcl definitely has Pygments support. If you press the edit button for Tcl and go immediately to Show Preview then the syntax highlighting appears.
For example:
is tan(atan(1/2)+atan(1/3)), 1;


I thought at first that there must be an unfinished tag or similar in the Swift entry but I can't see anything.
Here atan(1/2) and atan(1/3) produces floating point values.


It's the same on FireFox, Chrome and Safari so unlikely to be a browser problem.
--[[User:Soegaard|Soegaard]] ([[User talk:Soegaard|talk]]) 15:31, 1 June 2013 (UTC)


Any ideas on what could be causing it? --[[User:PureFox|PureFox]] ([[User talk:PureFox|talk]]) 16:38, 2 September 2023 (UTC)
== Spam redirect ==
(Posted this on Paddy's page a while back but he doesn't seem to be around atm, maybe you'd like to have a look at it.)


:Just looked at the [[100 doors]] task and the problem there is far worse as SH is gone after the Crystal entry - though again I can't see any obvious cause. Probably something to do with the WikiTide migration as I don't recall seeing this problem with Miraheze. --[[User:PureFox|PureFox]] ([[User talk:PureFox|talk]]) 17:34, 2 September 2023 (UTC)
Just found the following redirect. It seems to refer to a software company. http://rosettacode.org/mw/index.php?title=CalmoSoft_Fifteen_Puzzle_Game&redirect=no
[[User:Fwend|Fwend]] ([[User talk:Fwend|talk]]) 19:00, 26 February 2016 (UTC)


::Both [[List comprehensions]] and [[100 doors]] have a category "Pages with too many expensive parser function calls", which I suspect is something to do with it. If you edit the page as a whole and click Show preview, a message appears at the top of the page saying:
: Not spam exactly. More confusion on the part of a new user. As far I as I can determine, CalmoSoft is a person, not a company. That was [[User:CalmoSoft|Calmosoft]]s first contribution to the site, (the first of many) and an overly specific page description was entered. While it wasn't well planned, I don't think it was malicious. That being said, you are probably right, that page probably should be removed at this point. --[[User:Thundergnat|Thundergnat]] ([[User talk:Thundergnat|talk]]) 20:50, 19 March 2016 (UTC)
:::Warning: This page contains too many expensive parser function calls.
:::
:::It should have less than 99 calls, there are now 106 calls.
::I'm guessing that syntaxhighlight could be the expensive parser function call, though there are about 125 syntaxhighlights in [[List comprehensions]] before it stops... --[[User:Tigerofdarkness|Tigerofdarkness]] ([[User talk:Tigerofdarkness|talk]]) 17:58, 2 September 2023 (UTC)


:::Ah,that sounds like it could be the culprit though, if it is, the stewards may be reluctant to do anything about it, as some pages are slow to load as it is. --[[User:PureFox|PureFox]] ([[User talk:PureFox|talk]]) 18:58, 2 September 2023 (UTC)
== massive changes to Heronian triangles ==
Many many thanks for reverting the massive (and damaging) changes to the Rosetta Code task:   ''Heronian triangles''.


:::I did an experimental edit to [[List comprehensions#Python]] to change it from a rather greedy eight syntaxhighlight to one. (Feel free to undo that.) I wonder if changing the "too many expensive" from a redlink to a real page would a) work, and b) help, and, while I would do it for Phix, whether PureFox would be happy to ferret out similar edits when Wren fails to syntax highlight properly? I rather suspect we'd just have to live with/give up on the 373 on 100 doors, though, or perhaps split it into say A-G, H-N, O-U, and V-Z, or whatever works best?. PS: one thing I noted was that syntaxhighlights with no actual highlighter didn't count towards the limit. --[[User:Petelomax|Petelomax]] ([[User talk:Petelomax|talk]]) 20:51, 3 September 2023 (UTC)
I didn't want to start an editing war on the task's preamble, but I couldn't let the damaging and negatory changes to the two REXX language's entries, as well as their prologues and epilogues.


::::Well, after Pete’s experiments, it now seems certain that this is where the problem lies. TBH I doubt whether it’s worth the effort of trying to do something manually about this. A lot of tasks will be affected and only a few will be completely fixable. Even then you’d need to watch out for further languages being added which could mess them up again. --[[User:PureFox|PureFox]] ([[User talk:PureFox|talk]]) 22:34, 3 September 2023 (UTC)
As an aside, it was nice to get the '''Ring''' programming entry back from the graveyard after being eighty-sixed.


:It seems that the limit can be changed: https://www.mediawiki.org/wiki/Topic:Va147qvml961b47p [[User:Laurence|Laurence]] ([[User talk:Laurence|talk]]) 23:18, 3 September 2023 (UTC)
I did, however, sent a rather lengthy thingy to Paddy   (user Paddy3118, the original author of the task);   you should be able to read Paddy's discussion page for what I did, and I tried to explain some of my reasons for my complaint.


::Interesting. It seems that syntax highlighting has only been regarded as an expensive parser function call since version 1.39 which would explain why this wasn’t a problem when RC was hosted by Miraheze or was self-hosted. --[[User:PureFox|PureFox]] ([[User talk:PureFox|talk]]) 23:37, 3 September 2023 (UTC)
The revert you did of the massive changes didn't revert my latest trivial changes.   I guess Rosetta Code's (or Wiki's) reversion process works better than we hoped.


::: Sorry guys. Had an unanticipated major project at work and have had zero time for Rosetta Code for the past month. Things are starting to settle down, should be around more in the future. --[[User:Thundergnat|Thundergnat]] ([[User talk:Thundergnat|talk]]) 18:50, 30 September 2023 (UTC)
From now on, I'm going to have to keep a copy of my (REXX'es) prologues and/or epilogues.   I always keep a
:::: Relieved to hear it's not a health issue, which had crossed my mind. --[[User:Petelomax|Petelomax]] ([[User talk:Petelomax|talk]]) 13:39, 1 October 2023 (UTC)
backup copy of each of the REXX programs, but I don't bother with the extraneous text(s).   I had never thought
that people would be butchering my comments of my REXX programs,   ... but there ya have it.


==Changeable words==
Again, many thanks for your actions.   -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 23:42, 8 July 2016 (UTC)
Hi Thundergnat, just to let you know, the output of a large number of samples on the Changeable words task was changed in April 2021. The change was to replace committeewoman and committeewomen with committeeperson and committeepeople. I've changed it back. I assume the change was for "political correctness", just thought I'd advise you I realise you don't get much time for RC. --[[User:Tigerofdarkness|Tigerofdarkness]] ([[User talk:Tigerofdarkness|talk]]) 16:04, 12 November 2023 (UTC)


:Huh. Bizarre. I find I difficult to figure out what they were trying to achieve. ¯\_(ツ)_/¯ Ah well, no lasting harm done. Thanks. [[User:Thundergnat|Thundergnat]] ([[User talk:Thundergnat|talk]]) 01:07, 13 November 2023 (UTC)
:I really doubt that the change was malicious, and certainly not targeted at the REXX entry. It looked to me like he (I assume he) was looking at an earlier version of the page, made some edits to it and saved it without realizing the implications. It wasn't only the REXX and Ring entries affected; The ALGOL 68, ALGOL W, AutoHotkey, CoffeeScript, EchoLisp, Elixir, Fortran, FreeBASIC, Go, JavaScript ES5, Julia, Kotlin, Lua, Pascal, Phix, R, REXX 2nd version, Ring, Scala, Sidef and Tcl entries were deleted completely and several other implementation had edits rolled back.


:::: I hope you don't think that I implied it was malicious, just damaging   (which required a bit of work to re-instate essential "by hand" and viewing the before and after screens, which are a royal pain in the ole neckhole for cut 'n paste). --- I didn't dare to revert such a massive change (having used up my silver bullets long ago).   I had no idea that so many others programming entries were deleted completely.   -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 05:01, 9 July 2016 (UTC)


:For what it is worth, if you notice such a large scale destructive edit in the future, don't try to fix it piecemeal, bring it to my or one of the other admins attention and we can roll back / undo the edit with one click. However, we can only easily roll back the '''last''' edit without higher permissions, so once further edits have been made to the page it becomes much more tedious. I generally try to check the recent changes page at least 4-5 times a day to catch spam and unintended edits before they get out of hand. I can't be here all the time though. Cheers --[[User:Thundergnat|Thundergnat]] ([[User talk:Thundergnat|talk]]) 00:28, 9 July 2016 (UTC)

:: Will do.   I didn't try to fix the massive changes, I only tried to fix the (two REXX) entries that I authored; that way, if it didn't get rolled back, at least I corrected what I could.   -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 05:01, 9 July 2016 (UTC)

:After a cursory investigation, it looks like it had been reverted to the [http://rosettacode.org/mw/index.php?title=Heronian_triangles&oldid=200527 17:52 13 March 2015 version] of the page, which tellingly is exactly the same size.--[[User:Thundergnat|Thundergnat]] ([[User talk:Thundergnat|talk]]) 00:53, 9 July 2016 (UTC)

<br>
-----
<br>

For what it's worth department:

Perusing around some odd and dusty corners of the ole Google-net, ... er, I mean internet, &nbsp; I came
across several negative comments about the various tasks (and formats) concerning the Rosetta Code
website; &nbsp; some of the negatory statements were complaining about the loosey-goosey task
definitions (and the various flavors on how the tasks/problems are presented --- that is, not having a
more strict format, or even not having a common format), &nbsp; and also that the task requirements
are &nbsp; "all over the place" &nbsp; and most requirements aren't rigorous enough, and/or some such
words to that effect, &nbsp; and other minor complaints. &nbsp; That's why I argue about people
using &nbsp; ''number'' &nbsp; instead of &nbsp; ''integer'' &nbsp; and the like. &nbsp; I don't believe
I've ever won any of those changes &nbsp; (some task author defend their original wording as if their
first born's life depended on it).


To that end, I've been making minor changes &nbsp; (I assume you or others may have noticed) &nbsp; to
some &nbsp; (well, OK, OK, a not small number of) &nbsp; Rosetta Code task's preambles, &nbsp; mostly in the
manner of:
::* &nbsp; trying to have each task contain a &nbsp; ''';Task:''' &nbsp; section header --- this is more dangerous than ya think
::* &nbsp; changing &nbsp; ''';C.f.:''' &nbsp; to &nbsp; ''';Related tasks:''' &nbsp; whenever noticed
::* &nbsp; changing &nbsp; '''See also''' &nbsp; to &nbsp; ''';See also:''' &nbsp; section headers
::* &nbsp; using a larger font for most mathematical formulae, &nbsp; especially when:
:::::* &nbsp; Greek symbols are used
:::::* &nbsp; sub- and/or superscripts are used
:::::* &nbsp; when other hard-to-read glyphs are used
::* &nbsp; removing pronouns from the preamble: &nbsp; ... Your task is to ...
::* &nbsp; removing superfluous wording: &nbsp; ... The purpose of this task is to ...
::* &nbsp; more use of highlighted numbers and variable names instead of: &nbsp; ... where "x" is equal to b or c and ...
::* &nbsp; more use of bullet points (either plain or numbered) instead of long comma-separated continuous lists
::* &nbsp; separating all the multiple &nbsp; <nowiki> [[xxx]] &nbsp; and &nbsp; {{yyy}} </nowiki> &nbsp; thingys into distinct lines
::* &nbsp; adding whitespace for visual fidelity
::* &nbsp; adding whitespace where it makes the reading of the text easier, and adds fluidity to your perusing
::* &nbsp; adding whitespace before the first text, this ensures that the (above) stuff won't be abutted with the task preamble
::* &nbsp; adding whitespace before the TOC (table-of-contents)


... Regarding this last bullet, this has become a concern &nbsp; (in my mind) &nbsp; ever since the last major
Wiki's upgrade. &nbsp; Previously, the TOC (on my screen, using FireFox, FireFox Aurora, and/or Microsoft's
Internet Explorer), &nbsp; the list in the TOC was always a very light blue. &nbsp; Now the TOC list is white,
&nbsp; with nothing distinguishing it from the regular (the background, so to speak) &nbsp; Rosetta Code task
preamble.

It was this "sameness" that prompted me to add more whitespace before most TOC's to make it easier to find
the TOC when scrolling. &nbsp; The best of all worlds would be to have the "old" very light blue color
reinstated somehow. &nbsp; I have no idea where to change the TOC list color, but I'm sure it's possible.
<br>By the way, that very light blue is the same color as
the "box" for the &nbsp; <nowiki> <lang xxx> </nowiki> &nbsp; thingy.

I would like to add much more thingys &nbsp; (er, I mean &nbsp; '''Related tasks''') &nbsp; for a lot of
Rosetta Code tasks, but that's 'nother kettle of fish. &nbsp; (I used to do this kind of documentation for a
living for quite a few years --- and most programmers get quite territorial about "their"
wording (documentation) and don't take lightly to improvements and/or changes --- no-siree bob). &nbsp; Some
tasks already have a template, but I don't think I have the proper authority or permission to update those
templates, and even add one, for that matter. &nbsp; '''Primes''' are one such "category". &nbsp; There are
many others. &nbsp; It helps curious people to find other &nbsp; ''birds-of-a-feather'', &nbsp; especially
if they don't know the wording to use to perform searches for (maybe) obscure (or hard to define) algorithms
or procedures.

There has been some kickback here and there (reverts, but mostly deletions), and when it happens, I
don't push it further, as I've said, I've used up my silver bullets earlier. &nbsp; I also like to
add appropriate JPEGs to a task's preamble, &nbsp; but several have been deleted by one person, even
though those images on the right-side of the preamble don't use up real estate on the preamble part of
the Rosetta Code task. &nbsp; Ya can lead a horse to water, but ya can't push a rope. &nbsp; One guy
(same as above) is reverting more than a few of my preamble changes, so if it gets worse, I'll probably
just fade away from further changes. &nbsp; No sense in wasting time if I try to make improvements to
some task's preambles if it ruffles his feathers &nbsp; (or steps on his toes). &nbsp; Sometimes it feels
like pushing a chain uphill.
-- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 05:01, 9 July 2016 (UTC)

== Heronian triangles ==

Thank you for finding and correcting my edit on [[Heronian triangles]]! I have no idea what happened, but I certainly didn't mean to delete half the page. (I only happened across it just now.)

[[User:CRGreathouse|CRGreathouse]] ([[User talk:CRGreathouse|talk]]) 15:05, 26 August 2016 (UTC)

Latest revision as of 01:07, 13 November 2023

Archive of older talk page entries


Syntax highlighting disappearing after a certain point for some tasks

Take the List comprehensions task for example. It's fine up to and including the Swift entry but then disappears from Tcl onwards even though Tcl definitely has Pygments support. If you press the edit button for Tcl and go immediately to Show Preview then the syntax highlighting appears.

I thought at first that there must be an unfinished tag or similar in the Swift entry but I can't see anything.

It's the same on FireFox, Chrome and Safari so unlikely to be a browser problem.

Any ideas on what could be causing it? --PureFox (talk) 16:38, 2 September 2023 (UTC)

Just looked at the 100 doors task and the problem there is far worse as SH is gone after the Crystal entry - though again I can't see any obvious cause. Probably something to do with the WikiTide migration as I don't recall seeing this problem with Miraheze. --PureFox (talk) 17:34, 2 September 2023 (UTC)
Both List comprehensions and 100 doors have a category "Pages with too many expensive parser function calls", which I suspect is something to do with it. If you edit the page as a whole and click Show preview, a message appears at the top of the page saying:
Warning: This page contains too many expensive parser function calls.
It should have less than 99 calls, there are now 106 calls.
I'm guessing that syntaxhighlight could be the expensive parser function call, though there are about 125 syntaxhighlights in List comprehensions before it stops... --Tigerofdarkness (talk) 17:58, 2 September 2023 (UTC)
Ah,that sounds like it could be the culprit though, if it is, the stewards may be reluctant to do anything about it, as some pages are slow to load as it is. --PureFox (talk) 18:58, 2 September 2023 (UTC)
I did an experimental edit to List comprehensions#Python to change it from a rather greedy eight syntaxhighlight to one. (Feel free to undo that.) I wonder if changing the "too many expensive" from a redlink to a real page would a) work, and b) help, and, while I would do it for Phix, whether PureFox would be happy to ferret out similar edits when Wren fails to syntax highlight properly? I rather suspect we'd just have to live with/give up on the 373 on 100 doors, though, or perhaps split it into say A-G, H-N, O-U, and V-Z, or whatever works best?. PS: one thing I noted was that syntaxhighlights with no actual highlighter didn't count towards the limit. --Petelomax (talk) 20:51, 3 September 2023 (UTC)
Well, after Pete’s experiments, it now seems certain that this is where the problem lies. TBH I doubt whether it’s worth the effort of trying to do something manually about this. A lot of tasks will be affected and only a few will be completely fixable. Even then you’d need to watch out for further languages being added which could mess them up again. --PureFox (talk) 22:34, 3 September 2023 (UTC)
It seems that the limit can be changed: https://www.mediawiki.org/wiki/Topic:Va147qvml961b47p Laurence (talk) 23:18, 3 September 2023 (UTC)
Interesting. It seems that syntax highlighting has only been regarded as an expensive parser function call since version 1.39 which would explain why this wasn’t a problem when RC was hosted by Miraheze or was self-hosted. --PureFox (talk) 23:37, 3 September 2023 (UTC)
Sorry guys. Had an unanticipated major project at work and have had zero time for Rosetta Code for the past month. Things are starting to settle down, should be around more in the future. --Thundergnat (talk) 18:50, 30 September 2023 (UTC)
Relieved to hear it's not a health issue, which had crossed my mind. --Petelomax (talk) 13:39, 1 October 2023 (UTC)

Changeable words

Hi Thundergnat, just to let you know, the output of a large number of samples on the Changeable words task was changed in April 2021. The change was to replace committeewoman and committeewomen with committeeperson and committeepeople. I've changed it back. I assume the change was for "political correctness", just thought I'd advise you I realise you don't get much time for RC. --Tigerofdarkness (talk) 16:04, 12 November 2023 (UTC)

Huh. Bizarre. I find I difficult to figure out what they were trying to achieve. ¯\_(ツ)_/¯ Ah well, no lasting harm done. Thanks. Thundergnat (talk) 01:07, 13 November 2023 (UTC)