Tag Info

Hot answers tagged


Please report new issues or feature requests on our issue tracker! The work on making this a full-blown Github based project originally outlined in this answer is now complete. All further feature requests and bug reports should be directed at the Github issue tracker. status-completed I have taken the liberty of doing some organization. I have ...


See "How do comment @replies work?" and "@Peter works for Péter Török?". Comment replies will often work with unicode. EG: Péter Török can be reached by both @Peter and @Péter. These are the documented rules (Not checked against latest source) for converting user display_name to comment-reply @names: Remove any spaces. Single quotes, dots, dashes and ...


It would be nice to have a place other than in these answers for us to share setups. Could you provide one and link it to the main post? I thought about posting another question to deal with this, but wasn't sure if it belonged in stackapps or meta.stackapps.


status-completed Being active on multiple sites, I've had some special requirements. So I've made a fork based on v1.3.0, which includes the following additional features: a variable $MYUSERID$ in the comments gets replaced by your userID on the current site you can have site-specific messages The latter is done by adding an (optional) Site: ...


I've made a couple of fixes to make this work again. While I don't fork and ask for a merge, here it is a copy of my script for convenience, the modifications are indicated with comments. The matches of sites has been revised as well. // ==UserScript== // @name stackoverflow-comment-reply // @namespace stackapps // @description Add ...


feature-request status-completed (v1.0.1): metadata referring to the post being commented on For example, $SITENAME: the name of the current site (ex. Stack Apps) $SITEURL: the URL of the current site (ex. stackapps.com) $USERNAME: the owner of the post being commented on


status-completed The script doesn't work when sites are accessed via https. I believe you simply need to change // @include http://*stackoverflow.com/questions* to // @include http*://*stackoverflow.com/questions* I've changed this locally and it now works. I use the HTTPS Everywhere extension in Google Chrome so most sites I access are ...

Only top voted, non community-wiki answers of a minimum length are eligible