## No more re-typing the same comments over and over!

This script adds a little 'auto' link next to all comments boxes. When you click the link, you see a popup with 6 configurable auto-comments (canned responses), which you can easily click to insert.

This script was inspired by answers to this question on meta.

## Features

Note that the dialog only inserts the text, it doesn't send the comment, nor does it flag anything; this is so that you can check the text before posting!

### 2. Customize the texts

Simply double click on a comment text or description in order to customize it. Hit the 'reset' button if you screw up. This customization is currently per-site. Note that the "Welcome to $SITENAME$" text is automagically inserted if the user is 'new' (member for less than a week), so you don't need to add that to your custom text (but you can if you want to, see '9' below).

If you need more/less than the default 6 comments, just carry on reading...

### 3. Quick user info

The dialog also includes a mini-summary of the user's activity (because if they haven't been back in months, there's no point writing them a comment).

### 4. Automatic notification of new versions

The script will also notify you if a newer version is created.

### 5. Import/export of custom comments

This helps with transferring custom comments between sites. The export/import 'format' is also conveniently presented as markdown, so you can post it in an answer below, and let others benefit from your words of wisdom.

Note that you can also use the Import to create an arbitrary number of comments (the default is 6). If there are too many, you can use the show/hide desc link to gain a bit of space.

### 6. Remote source for comments

If you get bored with copy/pasting your comments between sites and/or computers, you can use the 'remote' button to define a remote source for your comment texts. See here for more details.

If you prefix your comment title with [Q], it will be only displayed for questions ([A] for answers). Non-prefixed comments are displayed for both.

### 8. [type here], [username] & [OP]

If the text [type here] is included in a comment, it will be automatically selected for completion when inserted. [username] will be replaced with the user's name (or just 'user' if nothing was found), and [OP] with the original poster's name (if found, else 'OP').

### 9. Customise welcome message

The default message is "Welcome to $SITENAME$" - which is shown for any 1-week-old users. By clicking on the 'welcome' link at the bottom of the popup, you can opt to change this message, or leave it empty to show no messages at all. You can also 'force' the message for older users on a one-off basis. This is per-site.

(Note, you may like this fork from Oliver Salzburg)

## Installation

Click HERE to install the user script. (warning Google are making things difficult for non-store user scripts. A workaround is explained here. Or use a script manager, like tampermonkey. NEW Derek has kindly uploaded the script into the Chrome store.

For other browser-specific instructions, read the instructions here)

## Update info

V1.2.9 - Fix for braking change (thanks SE devs!), suggested by PeeHaa. (Any other suggestions not including setTimeout are welcome!)

V1.2.8 - Update to take advantage of new 'draggable dialogue' functionality.

V1.2.7 - Correct bug noted by Oddthinking, and implement the 'force welcome' function requested by Martin Scharrer.

V1.2.6 - Implement the much-requested override for the new user Welcome message. Correct a bug with mangled markdown and another due to modified SE markup.

V1.2.5 - Implement [OP] tag as suggested by Gaffi. 'Fix' for markdown/html conversion bug reported by Madara Uchiha.

V1.2.4 - Modify code to get script working in new Review (reported by Oliver Salzburg), hat-tip to Shog9 for the fix.

V1.2.3 - Slight modification to remote dialogue (details here). You can now use [username] as a wildcard (as suggested by daviesgeek). Corrected & bug noted by Oliver Salzburg

V1.2.1 - update to work with 10k tools (suggested/implemented by ThiefMaster)

V1.2.0 - one fix (remove greeting before switching to edit mode), and one feature: hit Enter key to submit (suggested by Bruno Pereira). Note that this isn't a major change, it's just my version comparison is string-wise, so V1.1.10 won't work.

V1.1.9 - fixed nasty javascript regex backreference replace bug (reported by ThiefMaster). For explanations see here and here.

V1.1.8 - fixed 'jQuery 1.7.1' bug, which stopped insert button being enabled. (No idea why it stopped working - though judging from this, maybe it should never have worked, as I was using attr("disabled", ""))

V1.1.7 - create pseudo categories for differentiating between comments for questions and comments for answers (suggested by oers) - simply prefix the comment title with [Q] or [A]

V1.1.6 - make script work in /admin/dashboard (for moderators, requested/implemented by Sathya)

V1.1.5 - make script work in /review (requested by Gilles (now uses jquery delegate for attaching events)

V1.1.4 - if the text [type here] is included in a comment, it will be automatically selected for completion (requested by daviesgeek)

V1.1.3 - include Registered/Unregistered in user info (requested by waiwai933).

V1.1.2 - Fixed bug when using 'magic' links (reported by Alex)

V1.1.1 - If you have descriptions auto-hidden, the selected one will still be shown (suggested by Alex).

V1.1.0 - bug fix. (SE's full.js is now delayed at load, so the unbind('click') was undoing my click() - fix from @balpha).

V1.0.9 -
- a) removed upgrading bits from previous version
- c) now uses internal notification for announcing new versions - d) corrected the 'new versions announced once only' (it never worked AFAICT)
- e) corrected the $SITEURL$ escaping 'quirk'
- f) stopped using .owner class for userinfo - g) corrected bug which showed greeting twice.

V1.0.8 -
- a) Mend see-through code.
- b) Make storage more neighbour-friendly (add prefix, backwards compatible).
- c) Allow variable number of custom comments (can only be modified via import).
- e) Use 'selfupdatingscript' for update checks
- f) Revert $SITEURL$ to not contain the http://.

V1.0.7 - add an import/export function - can be used to transport custom comments between sites (note the use of $SITEURL$ and $SITENAME$ tags),

V1.0.6 - changes to the list of included urls

V1.0.5 - suppress warnings on new updates if already installed (previously each site would tell you about a new update, even if you'd already installed it)

V1.0.4 - corrected two bugs in code detecting the appropriate userid to lookup

V1.0.3 - corrected a bug in rep formatting. Integrated a function to poll once a day for new versions and notify user if any found.

V1.0.2 - implemented customisation, using HTML5 storage to allow users to create/modify their own messages

V1.0.1 - some refactoring, corrected a bug in the regex that converted html to markup.

## Note

Any comments welcome, whether on the functionality or the code.

Can be used in tandem with my other user script.

## Credits

• TomWij (below) created a modified version of the script, which inspired my V1.0.8
• balpha came up with the clever (evil) way to make the script 'self-updating'

## Known issues/Future plans

• The main future plan is to get this script adopted by SE. I like maintaining it, but some of the usability niggles (sharing across sites is still clunky, even with the remote option) can only be resolved centrally. (Vote here if you agree!)
• Modifying the script so that it also works in edit summary (as per this request), and the custom off-topic close reason (as per this request).
-
I suggest you move your code into a well-organized GitHub repo. Then you can take advantage of the built-in Wiki and Issue manager to handle documentation and feature request/bugs. I've seen the gist, and it's very large, do you think you should separate your code into several files that work together? See the CV-pls Extension –  Madara Uchiha Jan 12 at 11:01
Just recently, this has stopped working for me on Firefox 22.0. The "Auto" button just does not appear anymore. –  John Saunders Jul 24 at 19:02
Stopped working in Chrome too. Stack Exchange probably pushed an update that altered the DOM in some way. –  Madara Uchiha Jul 24 at 20:16
@MadaraUchiha see below (note, this is not an 'official' fix, just to let you know where to up vote :) –  Benjol Jul 25 at 4:44

marked as duplicate Dec 12 '13 at 16:36 UTC

This bug has been reported before and has already been heard. If those tags don't satisfy you, please don't ask the same question again.

'The previous bug is thankfully fixed, but...

When I import or write the comments, and click "save", the wrong titles are matched to the wrong comments, and some of them just lose their comments.

Also, the "A" and "Q" features do not work.

I'm using Chrome 30.0.1599.47 (Official Build 223717) beta-m, in case that matters.

###1
Please don't add "thanks" as answers. With just a bit more <s>money</s> reputation, you will gain sufficient [privileges](http://$SITEURL$/privileges) to upvote answers you like!!! You will also, then, be able to comment on the answers to say "+1! Thanks for the answer!" or something on the lines of that. Now, I'm just flagging this for deletion.

###2
Whilst this may theoretically answer the question, [it would be preferable](http://meta.stackoverflow.com/q/8259) to include the essential parts of the answer here, and provide the link for reference.

###3
This is really a comment, not an answer. With a bit more    rep, [you will be able to post comments](http://$SITEURL$/privileges/comment). For the moment I've added the comment for you, and I'm flagging this post for deletion.

###4

###5
If you have another question, please ask it by clicking the [Ask Question](http://$SITEURL$/questions/ask) button.

###6
If you have a NEW question, please ask it by clicking the [Ask Question](http://$SITEURL$/questions/ask) button. If you have sufficient reputation, [you may upvote](http://$SITEURL$/privileges/vote-up) the question. Alternatively, "star" it as a favorite and you will be notified of any new answers.

###7

###8
Please note that Non-mainstream questions are prohibited. Any instance of refuting currently accepted mainstream theories, such as General Relativity, or the Standard Model, is not allowed. Do not promote your own (or anybody else's, for that matter.) non-mainstream ideas. Anything which has not been published in a reputable journal is not mainstream. Physics is based on Mathematics. Popular Science is not real Physics. For more details, please see the [Non-mainstream Policy](http://meta.physics.stackexchange.com/questions/4538/is-non-mainstream-physics-appropriate-for-this-site).

###9
In future please reply to a user by using "@username", as I  have done here as an example. Else, they won't be notified. For example, to reply to me,  "@Dimension10", etc.

###10
You are asking for too many things in a question. You should ask each question as a separate question.

###11
Note that MathJax is supported here. Use it to render equations. If you are not familiar with MathJax, it is essentially LaTeX code (but it ***must*** be surrounded by $ signs for inline equations and $$ signs for other equations. E.g. $$E=\sum_{j=1}mc^3$$ results in$$E=\sum_{j=1}mc^3$$and $E=\sum_{j=1}mc^3 results in $E=\sum_{j=1}mc^3$. For a documentation of LaTeX, see [LaTeX](http://tobi.oetiker.ch/lshort/lshort.pdf)..

###12
If you have enough reputation to participate in [Meta](meta.physics.stackexchange.com) (that is 5 rep), you can try formatting at the [Sandbox](http://meta.physics.stackexchange.com/questions/389/formatting-sandbox). However, MathJax isn't supported at Meta (only on the main site, which is this), yet.

###13
You are expected to do a small search for the answer before asking questions here, as this way, it will be no effort on your part.

-

I would like to see some improvement to the "import/export" dialogue. Inserting any whitespace character (like a space) will result in something very undesirable. Example:

###Title 1
Text of comment 1

###Title 2
Text of comment 2


(note the space on the blank line) will, after clicking "save", turn into:

###Title 1
Text of comment 1

###Title 2



i.e. the space has replaced the text of my second comment (and the text has now vanished). It might also occur with multiple line breaks between two comments.

I got kind of frustrated when I lost most of my hand-crafted comments by this unexpected behaviour.

It is particularly nasty when editing one's comments in an editor (to avoid clicking outside the dialogue and losing all one's work) that uses CR+LF line endings -- the default for Windows.

Lastly, I'd like to have an easier way to add a new comment to my list -- this is currently only possible through the "import/export" dialogue, which can give rise to above drawbacks.

With that said, this script has saved me a lot of time, and I thank you for maintaining it!

-

I forked the script to create some quick-insert buttons.

Given how often I make use of this, I wanted to save the extra click.

-

(I won't deploy just yet, I'd prefer to group this with other updates)

Mini suggestion: Open the update link in a new tab.

-

(used this fix in V1.2.9)

Some people are experiencing a problem where the auto link does not appear. This has to do with the fact that the DOM elements on which the selector is based are dynamically loaded into the DOM.

The workaround for this is to change line 683 to:

setTimeout(function() {
$('#' + divid).find('.comment-help-link').parent().append(newspan); }, 10);  Basically this is just a minor time out before trying to add the link, which should not be noticeable. I'm not 100% sure about the 10 milliseconds, but it works for me (Chrome Canary). If it still doesn't appear for you try 100 milliseconds or something like that. - @Dimension10: the script auto-checks for updates everyday, so you can just wait. A new version will not override any customization of comment texts, no. – Benjol Aug 12 at 11:28 show 24 more comments As posting setups was mentioned being useful, here is mine: ###[Q]App recommendation Please note that recommendations like *Is there an app for X* are off-topic here (see [What topics can I ask about here?](http://$SITEURL$/help/on-topic) for details). For where your question might fit better, you might want to look into [Where can I ask questions that aren't Android Enthusiast questions?](http://meta.android.stackexchange.com/q/371/16575) ###[Q]Development question This site is for users of Android, which means that questions about development/programming are off-topic here (see [What topics can I ask about here?](http://$SITEURL$/help/on-topic)). Development questions are on-topic on our sister site [Stack Overflow](http://stackoverflow.com/questions/tagged/android). ###[Q]More than one question asked The question-and-answer format of this site works best if you put each question in a separate question post. Please edit your post down to one question, and create new posts to ask any further questions. You'll get better answers that way. ###[Q]OP providing facts in a comment The best way to add additional information to your question is by editing it, with the **edit** button. It is better visible that way, and comments are mainly for secondary, temporary purposes. Comments are removed under a variety of circumstances. Anything important to your question should be in the question itself. ###[A]OP adding a new question as an answer Remember this is a Q&A site - so keep on editing your question with new information - this section is for actual answers. If you have another question, please ask it by clicking the [Ask Question](http://$SITEURL$/questions/ask) button. ###[A]OP using an answer for further information This is a question-and-answer site, not a forum. Please use the **Post answer** button only if you have a solution to the problem, so that other users can see your question is not yet answered. You can click **edit** on the question to add more information to it. ###[A]Answers just to say Thanks! Please don't add "thanks" as answers. Invest some time in the site and you will gain sufficient [privileges](http://$SITEURL$/privileges) to upvote answers you like, which is the$SITENAME$way of saying thank you. ###[A]Nothing but a URL (and isn't spam) Whilst this may theoretically answer the question, [it would be preferable](http://meta.stackoverflow.com/q/8259) to include the essential parts of the answer here, and provide the link for reference. ###[A]Comments as an answer (new users) Please don't add comments as answers. Invest some time in the site and you will gain sufficient [privileges](http://$SITEURL$/privileges) to upvote answers you like, or to add actual comments when seeking clarification of any issues. ###[A]Comments as an answer (experienced users) Please don't add comments as answers. Use actual comments when seeking clarification of any issues. ###[A]Answer that is a question If you have another question, please ask it by clicking the [Ask Question](http://$SITEURL$/questions/ask) button. Include a link to this question if it helps provide context. ###[A]Requests to OP for further information This is really a comment, not an answer. With a bit more rep, [you will be able to post comments](http://$SITEURL$/privileges/comment). For the moment I've added the comment for you, and I'm flagging this post for deletion. ###[A]Another user adding a 'Me too!' If you have a NEW question, please ask it by clicking the [Ask Question](http://$SITEURL$/questions/ask) button. If you have sufficient reputation, [you may upvote](http://$SITEURL$/privileges/vote-up) the question. Alternatively, "star" it as a favorite and you will be notified of any new answers.  Entries #1 & #2 are specific to Android Enthusiasts, but similar cases might exist on other stacks, too. - add comment ## Feature Request Have a selector that is similar to [OP] but it would select the poster of the answerer instead of the question. This would obviously only apply to comments on answers. It could look something like [OAP] // stands for "Original Answer Poster" [AP] // stands for "Answer Poster"  - show 2 more comments (but not much time in the immediate future, if someone else wants to try...) ## Feature Request Can we have the auto link appear when completing a custom "off-topic" closure reason? Bonus points if we can declare certain auto-comments to apply in this scenario (e.g. mirroring the "A" and "Q" prefix for answers and questions). Perhaps "C" for closure reasons? - I just came here to ask the same thing - yes please. – Iain Jul 19 at 15:56 show 1 more comment (sort of) Google Chrome is now making it harder to install the script for security reasons. Upon clicking on the install link, a warning pops up refusing to install it. There's a Learn more link, recommending you use Google's oh-so-convenient distribution mechanism. (There is a workaround for the user hidden in the text, which I am about to try.) - show 3 more comments I have the problem that whenever I change or add any comments, my changes are gone after restarting my Firefox and all comments are back to the default values. Has anybody a hint what this could be caused by? I use FF19 on Ubuntu and Autocomments 1.2.8. I also wonder if the noscript addon of FF could have any influence but for the SX sites all scripts are allowed. Any hints or ideas? - show 1 more comment ### Bug Report I managed to install this with Tampermonkey on Google Chrome (Windows 7) along other scripts, except this script isn't working for me on Chrome (Firefox does work). - show 2 more comments I am excitedly using the "much-requested override for the new user Welcome message." in V1.2.6, as one of those requesters. The save function doesn't appear to be sticking. It works immediately, but when I come back later, it has returned to the default message. (Chrome, Windows) - Oddthinking, thanks for letting me know. Fixed (or should be!) in 1.2.7 – Benjol Jan 22 at 6:03 add comment At the moment the Welcome message for new users is not displayed if the question was migrated from a different SE site and the user does has an account on the target site yet. The message should be inserted in this case. - show 2 more comments There should be a method to force the insertion of the Welcome message. This can be required because some new users might have and account for 2-3 weeks already but just now started to post questions or answers. They might have found SE, registered an account but then didn't return for a while. Often these people still are new to the site and a Welcome message is appropriate, especially if it got changed to include a link to a special Welcome meta page (which I did for my site TeX.SE). - show 3 more comments Can $SITENAME$ be changed for Christianity? Here's what a comment to a new user reads: Welcome to Christianity! ... Which sounds pretty creepy. For one thing, most folks who stumble into the site are already affiliated with some faith, which might or might not be Christianity. For another, it sounds like we are a cult or a church. We aren't. Could $SITENAME$ be changed to "Christianity—Stack Exchange" or "Christianity.SE"? (I haven't tried to adjust the messages myself, but besides being a bit tedious, it probably would be best to not have new users of the script sending the wrong signals.) It's less of a concern, but I think it would be odd to see messages like: Welcome to English! ... or Welcome to Parenting! ... I forked a version and made the following changes at line 67: if(sitename == "Stack Exchange"){ sitename = arr[arr.length - 2]; //workaround for SE sites.. greeting = 'Welcome to ' + sitename + '—Stack Exchange! '; sitename = sitename + '.SE'; }  That way, the "Answers just to say Thanks!" comment reads: Welcome to Christianity—Stack Exchange! Please don't add "thanks" as answers. Invest some time in the site and you will gain sufficient privileges to upvote answers you like, which is the Christianity.SE way of saying thank you. The same comment on SO reads: Welcome to Stack Overflow! Please don't add "thanks" as answers. Invest some time in the site and you will gain sufficient privileges to upvote answers you like, which is the Stack Overflow way of saying thank you. - Typically lazy developer's response, how about *%SITENAME%*? – Benjol Mar 7 '12 at 7:13 the way I'm thinking about it right now, I think I'd be tempted to make the whole greeting configurable (there are some people who don't like it). I've got a few other changes in the pipes, so this may take a while. In the meantime, if you want to do a personal hack while you're waiting, you need to track down the user-script file, go to line 66, and replace sitename = arr[arr.length - 2]; with sitename = arr[arr.length - 2] + 'your_suffix_here';. After saving, you'll need to F5 in your browser to see the difference... – Benjol Mar 9 '12 at 6:44 Looks good to me, watch out, I've got a new version coming up, you'll need to rebase your fork :) – Benjol Mar 23 '12 at 14:56 show 9 more comments (You can now override this if you don't like it) Another bug: Every comment is prefixed with "Welcome to StackOverflow!" since recently. Doesn't seem to happen on all pages; http://stackoverflow.com/questions/9729546/jquery-script-being-executed-before-all-each-has-completed is one where it does happen though. - show 4 more comments (something equivalent, anyway) I see a couple of comments here suggesting that Benjol is thinking of making the Welcome message configurable. This is a formal request for that feature. On Skeptics.SE, we have a meta-post which is a Welcome to New Users FAQ, and explains some of the ways Skeptics.SE differs from other Stack Exchanges. I have experimentally forked this code, just to make the Welcome message include a link to this meta-post. Unfortunately, my JavaScript skills are too dodgy to make it customisable and offer it back to you as a patch. (The customisation strikes me as particularly tricky for the troublesome few that moderate multiple Stack Exchanges.) ## Suggested presentation: This is only a suggestion - incorporate it into the existing options file. It is a bit ugly, but I think better than having a whole separate config system. ~~~ This is comment text. This line represents the default. Welcome, my dearest new friend, to$SITENAME.

~~~[skeptics] Using the same 'restriction' notations as [Q] and [A], this overrides the default for one site.
[Welcome to Skeptics](http://meta.skeptics.stackexchange.com/questions/1505/welcome-to-new-users)!


An alternative would be to put it all on one line, but then the [qualifier] notation would conflict with the [link]() notation.

-

The following message breaks stuff (results in HTML being inserted) etc.:

[**Please, don't use mysql_* functions in new code**](http://bit.ly/phpmsql). They are no longer maintained [and are officially deprecated](https://wiki.php.net/rfc/mysql_deprecation). See the [**red box**](http://j.mp/Te9zIL)? Learn about [*prepared statements*](http://j.mp/T9hLWi) instead, and use [PDO](http://php.net/pdo) or [MySQLi](http://php.net/mysqli) - [this article](http://j.mp/QEx8IB) will help you decide which. If you choose PDO, [here is a good tutorial](http://j.mp/PoWehJ).

-

## Here's a bug report.

I've attempted to add the following comment:

[**Please, don't use mysql_* functions in new code**](http://bit.ly/phpmsql). They are no longer maintained and the [deprecation process](http://j.mp/Rj2iVR) has begun on it. See the [**red box**](http://j.mp/Te9zIL)? Learn about [*prepared statements*](http://j.mp/T9hLWi) instead, and use [PDO](http://php.net/pdo) or [MySQLi](http://php.net/mysqli) - [this article](http://j.mp/QEx8IB) will help you decide which. If you choose PDO, [here is a good tutorial](http://j.mp/PoWehJ).


Which should render like so:

Please, don't use mysql_* functions in new code. They are no longer maintained and the deprecation process has begun on it. See the red box? Learn about prepared statements instead, and use PDO or MySQLi - this article will help you decide which. If you choose PDO, here is a good tutorial.

Instead, right after saving, it renders to

[**Please, don't use mysql_* functions in new code***](http://bit.ly/phpmsql)*. They are no longer maintained and the [deprecation process](http://j.mp/Rj2iVR) has begun on it. See the [**red box**](http://j.mp/Te9zIL)? Learn about [</a>*<a href="http://j.mp/T9hLWi">prepared statements*](http://j.mp/T9hLWi) instead, and use [PDO](http://php.net/pdo) or [MySQLi](http://php.net/mysqli) - [this article](http://j.mp/QEx8IB) will help you decide which. If you choose PDO, [here is a good tutorial](http://j.mp/PoWehJ).


Which renders as

Please, don't use mysql_* functions in new code*. They are no longer maintained and the deprecation process has begun on it. See the red box? Learn about prepared statements* instead, and use PDO or MySQLi - this article will help you decide which. If you choose PDO, here is a good tutorial.

I suspect the asterisks are derailing it, but why should it care about it anyway? Does it attempt to also fix the comment before saving?

## Edit

Seems like the Comment's markdown is parsed into HTML and then remapped to Markdown (why?!). Using's Chrome's console and editing the localStorage directly with

<a href="http://bit.ly/phpmsql"><strong>Please, don't use <code>mysql_*</code> functions in new code</strong></a>. They are no longer maintained and the <a href="http://j.mp/Rj2iVR">deprecation process</a> has begun on it. See the <a href="http://j.mp/Te9zIL"><strong>red box</strong></a>? Learn about <a href="http://j.mp/T9hLWi"><em>prepared statements</em></a> instead, and use <a href="http://php.net/pdo">PDO</a> or <a href="http://php.net/mysqli">MySQLi</a> - <a href="http://j.mp/QEx8IB">this article</a> will help you decide which. If you choose PDO, <a href="http://j.mp/PoWehJ">here is a good tutorial</a>.


Appears to fix the problem.

-
to be honest, I can't remember when or why I decided to store it as HTML. Whatever, I've got a pseudo-correction in the works (very pseudo, it skips transformations of * and ** if it finds a backtick in the middle). –  Benjol Oct 25 '12 at 8:54

(sort-of, you can now customise the welcome message)

Bug observed with 1.2.4 and 1.2.5:

On some sites, instead of having the automatically-extracted site name in the comments, I get the question title. For example:

Welcome to Is Category Theory useful for learning functional programming?! Please don't add "thanks" as answers. Invest some time in the site and you will gain sufficient privileges to upvote answers you like, which is the Is Category Theory useful for learning functional programming? way of saying thank you.

This happens on Computer Science and Travel but not on Stack Overflow or Security or Stack Apps, so my guess is that whatever you're scraping there is a bit different on beta sites.

By the way, I would prefer to see Stack Exchange there (without the site name), at least on the sites which don't have a distinct branding (i.e. perhaps excepting SO, SU, SF and AU). Sentences like “Welcome to Computer Science!”, “the Travel way of saying thank you”, … don't make much sense.

-

Bug report:

Prefixing entries with [A] no longer shows these entries when adding a comment to an accepted answer. Only entries without a [A] or [Q] prefix are shown on such posts currently.

For my canned-messages set, where each entry is has either a [A] or [Q] marker, that means nothing is shown at all for accepted answers.

-

Can you add support for an Enter or Return keystroke to allow for insertion of the currently selected option? This would be really helpful! I have several custom comments and it can be a pain to scroll down to find the insert button.

-

Request: I see a lot of newbies post a comment saying "Thanks this worked perfect for me. It's exactly what I need" on an answer to their question, yet they do not mark the answer as accepted. [username] plugs in the username of the answerer when posting on an answer, but it would be helpful to also include an [OPusername] (or something to that effect) to be able to @ the original question asker on a specific answer.

i.e.

"If this answer is helpful to you, [OPusername], then please consider marking it as the accepted answer so others may more easily find it in the future. This is also a polite way to thank the person answering your question for helping you out."

-
Implemented, but using [OP] instead of [OPusername] –  Benjol Nov 1 '12 at 6:38

It seems like it isn't compatible with the new review system.

-

There are two 'major' changes to V1.2.2

### 'Remote' comment source

You can now define an external source for your comments, and 'import' them. This means that you don't have to manually copy comments from site to site and PC to PC.

To do this, you click on the 'remote' link; enter the url for your data source; then click on 'get now'.

The data source must be formatted as jsonp. There is a new 'jsonp' link in the import/export dialog which will create the appropriate jsonp from your existing comments.

It is also possible to automatically invoke it every time you open the dialog, by selecting the auto-get checkbox. I'm interested in feedback on this.

I've added a function to be able to 'broadcast' messages without changing the code. The intended use for this will be to ask for feedback on proposed future changes. Taken this off-line again, it was not completely thought-through and you had to dismiss on every site... (sigh, no global storage)

-
@jrg, actually, don't. There seem to be problems with parallel ajax queries here. While trying the next version I found the comments sometimes just disappear and never come back. –  Benjol May 23 '12 at 12:21

@Benjol You could add the extra set of comments that I use in-tandem with Phrase Express:

@<username> Please don’t use signatures or taglines in your posts. Every post you make is already "signed" with your standard user card, which links directly back to your user page

Shopping questions are off-topic as per the FAQ: it is not about a shopping or buying recommendation

-

Can you add multiple pages of comments? Currently if you have a lot of auto comments, you have to scroll to see them, but it would be nice to be able to click next and previous to see lists of about 5 comments.

Also, the "see through" feature is cool, but it should be activated by a click, instead of on mouse over.

One more problem: Importing the comments seems not to save them.

-
Hang on, is that Firefox 9 an upside-down six?! –  Benjol Sep 19 '11 at 13:32

It would be great to be able to use this same functionality in the edit summary when making edits. Most of the edits I do fall into a small subset of "categories" and it pains me to have to put in the same summary over and over.

To take it one step more, since edits may be for more than one thing at a time, a slightly different interface that is checkbox-based, rather than radio buttons would be ideal so that I could combine / chain the edits I've made.

In summary, here's what I am asking for (in order of priority / usefulness):

2. Adding a category for Edit Summaries
3. Changing the behavior for edit summaries to allow for adding multiple "comments"
-

I'd like to group my comments into

3. Both

And only the relevant comments will show, when I click the auto-link.

-
Bug: if my comment contains &, when I insert it it will insert &amp; instead.