Re: [Pharo-users] Working directory and image directory
I find the same anomalies in V9 for MacOS for workingDirectory pointing to root. I had to create a configuration system so I could effectively manage locations instead of using workingDirectory references. Other anomalies... when attempting to type in a (super) class in class creation - each keystroke launches debugger... same when setting up iceberg/github - typing in a package/folder name launches debugger with each keystroke... annoying, but I can get through it. Oh, this also seems to happen whenever I'm typing 'thisContext'. This all seems related to the type-ahead facility. Also a few observable issues with transmitTo: / sorting with Spec2 in V9... looks like when a column sorting issue was fixed it blew up transmitTo: ... -- sort - now sorts the pane but doesn't appropriately convey through the transmitTo: to the next pane - sometimes crashes, sometimes just doesn't display correct data... unusable, had to put this project on hold. I've asked here before how to submit a bug report - but didn't get a response (my posts are probably too benign for the experts, lol). If you know how to submit a bug report, I'd appreciate a (very) small primer or point me to a link. Thanks! Russ On Fri, Jul 31, 2020 at 6:29 AM Davide Varvello via Pharo-users < pharo-users@lists.pharo.org> wrote:
Hi
Isn't it weird this behavior for the community? Should I open a bug? Cheers Davide
Pharo Smalltalk Users mailing list wrote
Hi Guys, As I already described here:
http://forum.world.st/Fuel-FLSerializer-tests-are-not-working-pharo-8-td5120...
there is something weird on Pharo 8 (on Mac) because I'm running an image that is in the same directory of the Pharo.app but "FileLocator workingDirectory" give me the root directory.
I expected the same directory where there is Pharo.app Cheers Davide
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
-- Russ Whaley whaley.russ@gmail.com
Hi Russ, Here's how to submit a bug report. Fortunately, GitHub makes it easy and straightforward. Surf to https://github.com/pharo-project and find the particular project that's affected. I think in your case, you want "pharo": https://github.com/pharo-project/pharo Underneath "pharo-project/pharo" you'll see 7 links in a toolbar. Click on "Issues", which brings you here: https://github.com/pharo-project/pharo/issues On the right is a big green button, "New issue". Click that to get a bug entry form. You have a bug, so click the "Get started" button for "Bug report". Choose a good title, nicely worded, to be nice to the devs so they can get a good idea from just a glance. Short & sweet. (They prefer 50 characters or less, because your title becomes an email "Subject:" line.) There's a template bug report that tells you what they need from you. You can edit it or replace it with your bug report. Markdown is supported (and can help with readability). A "cheat sheet" is here: https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf and a more detailed explanation is here: https://guides.github.com/features/mastering-markdown/ The toolbar above the text area will apply the most-commonly-used markdown for you, with just a button click. Select text, click the associated button. You can click the "Preview" button to see how your markdown will be rendered in the submitted report; click on "Write" to return to the editable version you started with. Note that you can attached code, files, images, etc. to help explain. Just drag files into the text area of your report and they'll automagically be attached for you. Similarly, you can click where it says, "Attach files by dragging & dropping, selecting or pasting them" and it will open a file browser for you to point-and-click. When you're done, click "Submit new issue". That it! -t -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Russ, Here's a link; I created a GitHub gist in your honor: https://gist.github.com/tbrunz/4209026fabc44c5baf0a502f677b708c Please provide comments, improvements, corrections, or anything that will make it clearer for others who are in the same boat. Thanks! -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Ted, Thank you very much for these detailed instructions! I have copied them out for future use. I can see I'm going to very much enjoy your tutorials :) I hope to have time today to submit a couple issues I've run across. Did I see you submitted the workingDirectory/root bug? Thanks, Russ On Sun, Aug 2, 2020 at 11:50 AM tbrunz <wild.ideas@gmail.com> wrote:
Russ,
Here's a link; I created a GitHub gist in your honor:
https://gist.github.com/tbrunz/4209026fabc44c5baf0a502f677b708c
Please provide comments, improvements, corrections, or anything that will make it clearer for others who are in the same boat.
Thanks! -Ted
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
-- Russ Whaley whaley.russ@gmail.com
Hi Russ, No, I haven't submitted it. I figured it would be good practice for you to do so! -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
You might like these, too (for newbies): https://gist.github.com/tbrunz/f1d74353bdff7d40031b10d4220daaa9 https://gist.github.com/tbrunz/02d9a2f62053f8dfa4c229e5075d6796 -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
participants (2)
-
Russ Whaley -
tbrunz