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

Indentation tabs #25

Closed
Wurstbrotc5 opened this issue Jul 25, 2019 · 4 comments
Closed

Indentation tabs #25

Wurstbrotc5 opened this issue Jul 25, 2019 · 4 comments

Comments

@Wurstbrotc5
Copy link

Hi,

first of all, thank you for this great plugin!

One maybe small issue: The "active comments" (typing /** enter to generate a comment) always use tabs as indentation. Would it be possible to honor the tab/spaces settings from NPP?

Sadly some code receivers (projects, companies, whatever) are very strict about their tab/space preferance.

@dail8859
Copy link
Owner

Thanks for opening the issue.

Everything appears to be working correctly for me using Notepad++ v7.7.1 32-bit and DoxyIt v0.4.3

comment


You'll have to be a bit more specific on what versions you are using and if you are trying anything different than I tried above. Also you should probably try DoxyIt v0.4.4 if you haven't already. I don't think it is available through the Plugin Admin yet.

@Wurstbrotc5
Copy link
Author

Wurstbrotc5 commented Jul 26, 2019

Thank you for the response,

and sorry my description was wrong, the problem is not even the tab/space setting.

I realized now that a comment above an existing function whatever indentation the function has in the first line. (Of course existing code is not affected by Notepad++'s settings).

Probably this comment behaviour even is intentional (?)

In any case, I use Notepad++ 7.7 32bit, and tried Doxyit in both v0.4.3 and 0.4.4 (altough both report as 0.4.3 inside of the program). Temporarily removing all other plugins makes no difference

A screen recording too, with some dummy PHP code, behaving like that for both tab and space settings:

record

@dail8859
Copy link
Owner

Probably this comment behaviour even is intentional (?)

Yes. It intentionally matches the whitespace of the function definition (even if that whitespace is a mixture of tabs/spaces), regardless of the actual editor setting. Maybe not a great example I put together previous, but you get the point. Also if comment blocks are expanded it keeps whatever whitespace indentation is being used.

(altough both report as 0.4.3 inside of the program)

Good catch. That one is my mistake.

@Wurstbrotc5
Copy link
Author

Ok, then I'll close this.
Thank you for your time

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

No branches or pull requests

2 participants