User talk:Markhobley

Welcome to Rosetta Code! I'm Mike, and I noticed you created an account.

Some quick things you should be aware of:

Template:Mylang	Helps you show what languages you're familiar with, and helps us become aware of skills with languages we haven't seen.
Category:Unimplemented tasks by language	A place to find tasks missing solutions in various languages.
Blogs, twitter, facebook...	We have them, and are interested in yours.
Special:Webchat	Logs you into #rosettacode on the Freenode IRC channel. Not usually the most active communications medium, but occasionally helpful. It's logged at http://irclog.perlgeek.de/rosettacode/today.
Rosetta Code:Village Pump	A general Q/A and discussion area.
Rosetta Code:Finances	For most of Rosetta Code's history, expenses have been paid out of my pocket. I can't afford that much longer, and so you can see the state of Rosetta Code's finances, and how you may help. If you enjoy or are excited about the site, please consider reading through it.

Sorry for the boilerplate; it can be a bit difficult giving an individual greeting to each person. If you post information about your technical interests and background, I'll probably read it. If you already have put that kind of information on your user page, I probably already have; I'm always interested in how people do and can benefit from Rosetta Code. --Michael Mol 02:57, 3 October 2010 (UTC)

Please include edit summaries

Just a little note: when editing, it's polite to include something in the summary that says what you've done -- for example, if you add a new solution to a task, it's nice to put something like "added language" in the summary so that others can see what you've done. -- Erik Siers 06:20, 3 October 2010 (UTC)

On that topic, there are options under Special:Preferences if one would like the wiki software to provide a reminder on such things. --Michael Mol 12:30, 3 October 2010 (UTC)

Tasks and placeholders

I very much appreciate your work at the creation of those terminal control tasks. Note, however, that by using Template:Task, a page gets registered as a task on Rosetta Code, and shows up in "tasks not implemented in language X" pages until an instance of Template:header shows up on the page, corresponding to language X. With the placeholders as they are on those terminal pages(such as the ones you have), languages are assumed by the system to be completed, even though there isn't any code. Normally, the process would be to create a task page, and only include Template:header for existing blocks of code on the page. Also, check out the recently-created Rosetta Code:Add a Task page, and see if there's anything we can do to help make it clearer and more useful.

Again, thanks! --Michael Mol 22:26, 4 October 2010 (UTC)

ZX Spectrum Basic

ZX Spectrum Basic seems to be considered a separate language from BASIC. As such, it should be placed in alphabetical order just like Visual Basic. If you want it to be included under BASIC headers, propose that it be considered a BASIC implementation and not a separate language, and then use {{works with}} to separate the examples under =={{header|BASIC}}==. --Mwn3d 18:39, 9 May 2011 (UTC)

Signature form

Hey Mark. I love the kind of work and directions you're pushing content on RC; it's good to see growth and exploration of areas we haven't touched on much. However, I'd like to ask you to change two things about how you use the Talk pages.

First, When you reply to someone, you'll often see a number of ":" preceding their paragraphs. That's indentation to emulate comment threading/nesting. If the person you're replying to has two ":" in front of their paragraph, please leave three in front of your paragraphs. If they have one, please leave two. If they have, none, please leave one. That helps observers like me cleanly keep track of who's replying to whom.

Second, when you reply, sign your last paragraph with --~~~~. This will be replaced by the wiki engine with a signature for you, including a timestamp. This helps observers keep track of who said what (without having to watch the history of the page), and when replies occurred. You can customize that signature somewhat by filling in the "real name" field under Special:Preferences.

Again, I like how things are working out, but I've just got those two things to bring up... --Michael Mol 15:37, 2 June 2011 (UTC)

Omit

Hi, Coud you perhaps put your 'omits' as minor edits? Thanks. --Paddy3118 18:52, 7 July 2011 (UTC)

Ta! --Paddy3118 03:05, 8 July 2011 (UTC)

VList changes

I see that you were changing the VList page. Do you think there's any chance of rescuing that page? It doesn't have an implementation at all, just an interface definition (of the highly “so what?” flavour, too) in a single language. If we can't rescue it, killing it off would be better I suppose. –Donal Fellows 14:58, 21 July 2011 (UTC)

File I/O GUISS

I admit I don't know if "Copy" does something extra in GUISS, but it looks like there should be a "paste"-type operation in between "Copy" and "Rightclick:Copy of input.txt" in that example. Is there something more to the "Copy" command (besides clicking on "Copy" in the menu)? --Mwn3d 20:52, 21 September 2011 (UTC)

GUISS Specifications?

I notice a bunch of GUISS examples you've posted, but there is no way to test them. If you could upload the GUISS specifications somewhere, someone might make at least a partial implementation. (A lot of it seems fairly simple to do in C++ or AutoHotkey) --Crazyfirex 01:11, 8 October 2011 (UTC)

GUISS Specification + Questions

Hello, Mark. I have some questions and also want to talk about GUISS.

If both Hotpop and yi.org are discontinued, then why you didn't switch to other services?
Why did you protect your Twitter account? And when did you protect it?

Now here are the questions about GUISS:

How to write a program in GUISS?
What operating system did you write your GUISS programs for?

And the most important question:

Do you still have the GUISS specification? Is it available in PDF? If so, upload it to ufile.io with an account.

Jazzedpineda (talk) 13:08, 20 December 2021 (UTC)