A long time ago there was a feature request asking to add increase/decrease indent buttons to the editor toolbar:

These should work by adding spaces or removing spaces from the beginning of the current line or every line between the start and end of a text selection (inclusive).

What was being asked for is something like this in the post editor:

indent/outdent buttons

So that poorly indented code like this can be formatted easier without being forced to use copy/paste and an external editor or hammering the space bar:

while(true) {
if (this) {
if (that) {

The linked question doesn't have a feature-request status tag and does have an accepted answer which apparently is a bit of a problem. So, in accordance with advice in this post here on meta:

Please add +/- indent buttons to the standard editor toolbar

Why ask this question again?

Seems some clarification on my motives are necessary so:

Does an accepted answer influence/affect a feature request at all?

It can cause some confusion as to whether the request has been handled or not ... We actively encourage users not to accept answers on feature requests that haven't been acknowledged for this very reason. - animuson♦

The linked request has an accepted answer but is neither implemented, declined nor acknowledged. I don't know whether it's even on the team's radar as there is no open question related to it (there are many closed duplicates) - Yet I feel would be quite beneficial. I'd be more than satisfied with an official "we know about that request and concluded status-meh" but there is no response and being a question with an accepted answer implies incorrectly it doesn't need one.

Better bump is editing existing requests - Shadow Wizard

That doesn't un-accept an answer - I don't know if that has any impact on "The Stack Exchange devs have a tool that lists feature-request-tagged posts across the network" - does it?

or adding bounty - Shadow Wizard

I can do that - does it achieve anything though? Again, I can find no references as to whether that affects the SE dev's tool or not.

not posting deliberate duplicates - Shadow Wizard

If the answer I've referenced is not the right way to bump an existing feature request - is there a reference for what is the right way to do it? I remain somewhat confused as to whether I've found and followed the wrong advice.

  • 2
    @ShadowWizard May I ask why you've flagged this as a duplicate of the question I'm trying to bump?
    – AD7six
    Commented Jun 5, 2014 at 10:35
  • Because time is not a factor. If something was already asked, asking it again is a duplicate no matter how you will try to paint it. I'm not saying delete this one, dupes are fine, but proper action is closing it. Better bump is editing existing requests, adding answers or adding bounty, not posting deliberate duplicates. Commented Jun 5, 2014 at 10:42
  • Is the answer to this post inaccurate, or is this comment inaccurate? If this is closed as a duplicate the feature-request will again, surely, become invisible or at least reach no visible conclusion.
    – AD7six
    Commented Jun 5, 2014 at 10:44
  • 1
    @AD7six: Because this is not the way to bump an existing feature request. You could put a bounty on that old post instead. Commented Jun 5, 2014 at 10:51
  • There are thousands of feature requests, the team can't possibly answer to all of them. They pick some sometimes, we can't have control over this. Bumping with edit or bounty gives it a chance, other than that really nothing we can do, and surely asking same thing again as new question every X days/weeks/months won't help. (dupes are useful for easier search, adding more possible keywords) Commented Jun 5, 2014 at 10:52
  • @AD7six: And feature requests are just that: requests. If developer resources come available and it is thought to be a priority, it'll be implemented. Otherwise, not so much. You can vote on such posts, and bounties also help make it more visibible. Votes on feature requests are one factor that can make a feature request increase in priority. Commented Jun 5, 2014 at 10:53
  • It has a status: status-meh. The devs don't care enough about it to plan for it, nor do choose to decline it. It is on the 'nice-to-have' pile, the 'when-we-get-to-it'. There is no more specific status for that. Commented Jun 5, 2014 at 12:21
  • Ironic dupe closure is ironic.
    – user1228
    Commented Jun 5, 2014 at 14:06


Browse other questions tagged .