Difference between revisions of "User talk:Jralls"

Latest revision as of 15:51, 1 November 2022

Page request

Hello John, Thanks for adding me as a Wiki user. I don't have sufficient privileges to create the page GncArchive.pl referenced from my update to Closing Books. Could you create the page for me? -Mike

Done. Please create a new section and add your sign on talk pages. --Fell (talk) 22:07, 26 June 2019 (UTC)

Revert discussion

Hello John, please explain your revert at the talkpage of Roadmap. Otto (talk) 14:11, 29 June 2015 (UTC)

Alias

Hi John, you took out the word alias from your last edit of the Editing Git page but I think you forgot to replace it with something better. Regards Chris Good

Chris, Thanks for noticing. Fixed.

Bugs/support for "unsupported" tool Bayes.perl

Hello, Jralls, many thanks for all your work on GnuCash. Your diligence includes monitoring the Wiki, and noticing the bugs I documented in Talk:Bayes. You deleted those notes, and pointed me to gnucash-user@gnucash.org to request support there.

Fair enough. I want to contribute in the correct way to help GnuCash forward. Still, the issues I was noting are for a Perl script at Bayes, and it says there, "The GnuCash team is not responsible for it and it is provided as-is and you can use it at your own risk." Do you really want traffic on gnucash-user for a "not responsible" bit of code? Do you also want bugs on this utility to be filed at bugzilla.gnome.org? If so, then is it all right if I add this after the "not responsibile" sentence in Bayes?

Thank you again for your dedication. I appreciate GnuCash very much. Jim DeLaHunt (talk) 19:16, 11 February 2016 (UTC)

Jim, if you open the history of the Bayes page, you can see the author User:YeOldHinnerk. How about contacting him? --Fell (talk) 22:26, 11 February 2016 (UTC)

Thank you, that is a good suggestion, but I'm not thinking so much of answering my questions as helping the next reader find the right way to answer their questions. The page should say what is the right place to direct questions and bug reports. Jim DeLaHunt (talk) 01:40, 12 February 2016 (UTC)

And BTW he's been in the past a regular contributor to gnucash-users, though he hasn't posted anything there in a year.

No, don't file a bug report for a Wiki page. Change the Wiki Page. We don't use Talk pages much. Frank and I camp out on the Recent_Changes page so that we can revert and block spammers, so we see the changes. I don't think that anyone else ever looks, so your complaints would be unheard. Much better to either change the page itself, to post about it on gnucash-user, or both.

FWIW a cursory look at the code shows that it has no facility for handling a compressed file and that it loops through the file once, processing the first import-map-bayes element that it finds and then exiting. It's working with the XML as raw text so it has the potential to mess up your file and make it unreadable. A simple XSLT stylesheet would do a better job more safely.

Thank you, Jralls. I will improve the wiki page. The XSLT suggestion is a good one. I'll have a go at that. Jim DeLaHunt (talk) 01:42, 12 February 2016 (UTC)

SQL Queries

Hi. Regarding your comment in http://wiki.gnucash.org/wiki/User_talk:G2010a: AFAIK that was my example. I removed it to reduce clutter and decided on a git repository so others can contribute queries and corrections (I noticed I have done several corrections to my queries without ever updating the wiki). Would you mind re-applying the changes? Thanks! - g2010a

Minor edits from Lee

Hi Jralls! I am working my way through MacOSX/Quartz. Thanks so much for putting this guide together! I have not gotten very far yet, but, in the spirit of giving back, I thought I'd try to make minor helpful edits as I progress. Hopefully you'll agree the edits are helpful. LeeRead (talk) 18:24, 31 July 2017 (UTC)

LeeRead: I would mind less if the changes were correct. There's no good reason to replace a clickable download link with a curl command line that has to be pasted somewhere, and anyone who's building GnuCash from source darn well ought to know her way around a browser well enough to be able to control-click the link and save it where they want, or to copy the link and paste it into curl on the command line. Please do keep the wording somewhat formal and succinct. For example, I don't particularly care for "This is well documented over at MediaWiki. Go there, read up, follow the recommended editing conventions, and you'll be communicating with fellow editors like a rock star in no time." A simple "MediaWiki has some talk page editing [<link> recommendations]." gets the same message across without sounding like a hipster chatbot.John Ralls (talk) 20:24, 31 July 2017 (UTC)

Sooo... nothing positive to say? :-) LeeRead (talk) 20:47, 31 July 2017 (UTC)

Sure. Your explanations of creating custom reports are very welcome indeed. That's always been a particular weak spot in our documentation.John Ralls (talk) 08:30, 1 August 2017 (UTC)

John, I get the feeling I stepped on your toes with my edits of your MacOSX/Quartz page. I like my changes, but it is your page, so we can revert if you like. LeeRead (talk) 10:38, 1 August 2017 (UTC)

It's not a stepping-on-toes thing. Your change is dumb. Why make the user paste a command line into the terminal when simply clicking the link and hitting command-s does the job?John Ralls (talk) 15:52, 2 August 2017 (UTC)

Oh sorry, just noticed this reply now! You are so hard on me! :-) I would argue that "dumb" is subjective here. Browsers sometimes change the filename extensions. I like the certainty of getting what you expect where you expect it with the curl command. LeeRead (talk) 00:00, 18 August 2017 (UTC)

MacOSX/Quartz updated with build notes

Hi John, as discussed on IRC, I've incorporated my notes from a successful build on gnucash stable on macOS into MacOSX/Quartz. Thanks for all your help with build issues. Some of my notes likely do not apply to gnucash unstable. Some of my notes might better belong on Building GTK-OSX. Some notes might be avoidable if we update source. Let me know what you think. And try to be gentle, eh? LeeRead (talk) 00:10, 18 August 2017 (UTC)

32Bit vs 64Bit

John, Sorry, I did not see your last edit of this page before I asked in gnucash-devel about my problem with the args to setup-mingw64.ps1.

I think this also needs to change:

Running a build Next open the Start menu and navigate to MSYS2 64Bit or MSYS2 32Bit; which you want will depend upon the bitness of your Windows version.

That's the reason I was trying to build the 64 bit GnuCash.

Maybe: depend upon the bitness of the version you are building.

Regards, Chris Good

Chris, you're right. Plus MSYS2 now supports only 64-bit Windows and doesn't have a 32-bit installer any more. Time to overhaul the page, I guess. John Ralls (talk) 04:44, 16 January 2022 (UTC)

Template:MacosPackage edit has spurious heading?

Hello, John:

Many thanks for all your work on GnuCash. Today I learned that it includes setting up a clever series of templates to help keep the macOS documentation on the wiki up-to-date.

However, the 22. June edit to Template:MacosPackage, updating it from 5.9-4 to 5.9-1, also included what seems like a spurious line break and `== Headline text ==` markup. (Maybe from bumping a formatting toolbar button.) This makes other pages look goofy, for example Template:Macos_Downloads and MacOS/Quartz.

I don't mind being bold and removing what looks like the extra text, but I wanted to check with you first to make sure there wasn't something deeper going on which I wasn't seeing. If you care to make the correction, please do. If you are OK with me making the correction, please let me know. And if I am missing something, please tell me to hold off.

Thanks again, Jim DeLaHunt (talk) 02:28, 31 October 2022 (UTC)

Jim, it's actually Frank Ellenberg who set up all of the templates. I just update them at release time, but you're right that I screwed it up last month. The Docs one had the same bogus entry, both fixed now. Thanks for pointing it out. John Ralls 02:59, 31 October 2022 (UTC)

Thank you for the prompt fix. There was still an interrupted link in MacOS/Quartz. I suspect that might be because of a blank line in TemplateMacosPackage. I went ahead and deleted that blank line there, and in Template:DocPackage. The links in MacOS/Quartz look fine now. Jim DeLaHunt (talk) 19:50, 31 October 2022 (UTC)

John, for what it's worth, the reversion https://wiki.gnucash.org/wiki/index.php?title=Template:MacosPackage&curid=4013&diff=21386&oldid=21382 has broken a link at MacOS/Quartz. It now reads:

...[https://downloads.sourceforge.net/sourceforge/gnucash/Gnucash-Intel-

4.12-1.dmg Gnucash-Intel- 4.12-1] is now available for download…

Jim DeLaHunt (talk) 04:53, 1 November 2022 (UTC)

Jim, I looked at history and saw that before the September release the newline goes between the text and the category. Now the Template:Macos_Downloads looks right. John Ralls (talk) 14:05, 1 November 2022 (UTC)

Thank you. The download link in MacOS/Quartz looks correct now, also. Linebreak before == significant, linebreak after <> significant, who'da thunk it? Jim DeLaHunt (talk) 15:51, 1 November 2022 (UTC)