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

Comments introduced by Ctrl+1 don't respect indentation #1938

Closed
spyder-bot opened this issue Feb 17, 2015 · 2 comments
Closed

Comments introduced by Ctrl+1 don't respect indentation #1938

spyder-bot opened this issue Feb 17, 2015 · 2 comments

Comments

@spyder-bot
Copy link
Collaborator

From [email protected] on 2014-08-19T20:27:34Z

Spyder Version: 2.2.5
Python Version: 2.7.8
Qt Version : 4.8.6, PyQt4 (API v2) 4.11.1 on Windows
pyflakes >=0.5.0: None (OK)
pep8 >=0.6 : 1.5.7 (OK)
IPython >=0.13 : 2.1.0 (OK)
rope >=0.9.2 : 0.9.4 (OK)
sphinx >=0.6.6 : None (NOK)
matplotlib >=1.0: None (NOK)
sympy >=0.7.0 : None (NOK)
pylint >=0.25 : None (NOK)

What steps will reproduce the problem?

While commenting code with Ctrl+1, the comment symbol is not shown after the right indentation, instead it always shows at the left side of the line, how can I solve this, is there any configuration for this?

Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1938

@spyder-bot
Copy link
Collaborator Author

From ccordoba12 on 2014-11-18T17:47:51Z

We have always introduced comments that way but we plan to change that in our next mayor release (i.e 2.4), as part of code folding.

Summary: Comments introduced by Ctrl+1 don't respect indentation (was: Comment not after right indentation)
Status: Accepted
Owner: [email protected]
Labels: MS-v2.4

@goanpeca goanpeca self-assigned this Apr 12, 2015
@ccordoba12 ccordoba12 modified the milestones: v3.0, v3.0beta4 Jan 27, 2016
@ccordoba12 ccordoba12 modified the milestones: v3.0beta4, v3.1 Apr 25, 2016
@goanpeca goanpeca removed their assignment Jan 14, 2017
@ccordoba12 ccordoba12 removed this from the v3.x milestone Jan 31, 2017
@ccordoba12
Copy link
Member

Closing as a duplicate of issue #1785

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

3 participants