Github code posting

Just posting to let know about a small posting to my GITHUB account. Some bits of code that i have written privately and not used since.

message() box function rewrite.
Search/replace function that i wrote one night and then did not use.
ShellEx function including direct print option.

Posted as Clarion 9.1 app file.

Free to use, no formal support provided.

Please let me know what you think.

find the code here…

Richard Bryce

If you include the generated code, then we can see what you’ve written directly in GitHub, without having to clone the repo, open the app, and generate the app.

Also, if you maintain the repo for the generated source, we can see what’s changed over time (bug fixes, enhancements etc)

FWIW, GitHub has Gists which are handy little automagic repos for a couple of files, which are related, such as the 3 things you mentioned above.

And even better, if you post a Gist link into Clarionhub (on a line by itself) the code will be automagically rendered in the topic/post.

Thanks for replying, I have now added the generated .clw files for this example so you can review the code online.

Gists, do you have an example here on clarionhub that i can have a look at.


Richard Bryce.

Hi Brahn,
thanks for replying.

can you point me to an example where you have used a Gists here on clarionhub.

Richard Bryce


How to use the code i have posted, pretty easy actually.

  1. go to this url.

  2. this page appears.

  3. Then click the download button that i highlighted “Cloan or download”

Clarion9 is required to view the .app file. Or view/edit the .clw files. Please Note, these examples have setups in both Global Data and Global Map embed points. Message box example also has setup code in Main() procedure, ThisWindow.Init method (embed point).


Richard Bryce

1 Like

#Where possible, avoid the download button, clone the repo instead#


Well the ZIP’d version of a git repos just has the content of each file.
Which means, that there is a good chance you’ll wind up with unix line endings on your files. and that’s bad because the clarion compiler fails when it encounters unix line endings.

On the other hand (OTOH), when you do a clone the git understands the target operating system and it automatically corrects line endings.

BTW, cloning is easier than downloading a .zip and then unzipping the zip anyway
you just clone a folder, it downloads the content and expands it all in one shot.

###How to configure your git repo’s to use windows line endings.###

1 Like