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

Change filetype defs seem to don't have any effect #7

Closed
frlan opened this issue Apr 25, 2017 · 6 comments
Closed

Change filetype defs seem to don't have any effect #7

frlan opened this issue Apr 25, 2017 · 6 comments

Comments

@frlan
Copy link
Member

frlan commented Apr 25, 2017

I've updated the filetype-defintions for python via the Tools->Configuration Files->Filetype Configuration->Scripting Languages->fileytypes.python and added

[indentation]
width=4
type=0

which should be also the default. But even after restarting Geany when opening a Python-file default indent is done via \t. (1.30.1 on 10.11.6)

@elextr
Copy link
Member

elextr commented Apr 25, 2017

Is it being overridden by a project?

@frlan
Copy link
Member Author

frlan commented Apr 25, 2017

No, it isn't

@frlan
Copy link
Member Author

frlan commented Apr 25, 2017

At least there is no open project according to the project menu.

@techee
Copy link
Member

techee commented Apr 25, 2017

@frlan I just tried and it works for me on Mac too. Are you sure you closed the file before retrying? (Otherwise the indentation type is stored into the session file.). Also don't you use indentation autodetection which could override it?

I don't think spaces are default for Python - the default is to use global or project settings.

That said, there really is a bug - the local filetype config file should be created based on the global one which doesn't happen now. I've just fixed it in

geany/geany#1482

@elextr
Copy link
Member

elextr commented Apr 26, 2017

Seems to work for me, but then I usually use spaces for everything so all my settings are spaces and maybe its one I forgot to change back to tabs that is making it work.

@techee
Copy link
Member

techee commented Oct 23, 2019

I can't reproduce the bug (or it's fixed) so closing. Feel free to reopen it if you still experience the problem.

@techee techee closed this as completed Oct 23, 2019
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

3 participants