Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elastic tabstops #288

Closed
ghost opened this issue Jun 9, 2014 · 8 comments
Closed

Elastic tabstops #288

ghost opened this issue Jun 9, 2014 · 8 comments

Comments

@ghost
Copy link

ghost commented Jun 9, 2014

See: http://nickgravgaard.com/elastictabstops/news/scintilla-implementation

Would be pretty neat to see in geany.

@b4n b4n added the enhancement label Jun 9, 2014
@b4n
Copy link
Member

b4n commented Jun 9, 2014

If upstream Scintilla implements it, it's likely we may support it, but otherwise we won't.

@b4n b4n added the Scintilla label Jun 9, 2014
@kugel-
Copy link
Member

kugel- commented Apr 3, 2018

Still not implemented in scintilla

@codebrainz
Copy link
Member

This hasn't been implemented yet, not sure why it's closed.

@kugel-
Copy link
Member

kugel- commented Jul 24, 2018

Because I set the pending timeout tag ages ago and there's been no activity since then.

@codebrainz
Copy link
Member

But it's not implemented yet, despite the several months of having a pending timeout label.

@kugel-
Copy link
Member

kugel- commented Jul 24, 2018

So? Its clear to me that it won't be implemented anytime soon. Why keep feature requests open forever with no activity?

@elextr
Copy link
Member

elextr commented Jul 24, 2018

Since this is dependent on an upstream feature request that hasn't seen any activity since 2014 I also suspect it isn't going to happen.

But @kugel-, since setting your "pending timeout" label does not prompt anybody, you need to also post some text to tell those watching that you have put their request on a short fuse unless there is some indication of activity, so that they know about it and can object if they are still interested. It is unreasonable to silently put a target on the request without notifying anybody interested before pulling the trigger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants