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

Auto-indentation fails when using splitwindow plugin #2732

Open
atarax42 opened this issue Jan 20, 2021 · 3 comments
Open

Auto-indentation fails when using splitwindow plugin #2732

atarax42 opened this issue Jan 20, 2021 · 3 comments

Comments

@atarax42
Copy link

When using the splitwindow plugin auto-indentation for a new line is not applied (when activated in settings > editor > indentation), instead the cursor is set to the first position of the new line. This is valid for the lower resp. right panel of the split window. In the upper resp. left panel indentation works as expected.

(using Geany 1.36 on Linux Mint)

@elextr
Copy link
Member

elextr commented Jan 20, 2021

If this is in the second pane, then its not unexpected, the second pane has limited functionality and is best considered a read-only pane.

Also split-window is in the geany repo, not geany-plugins, moved.

@elextr elextr transferred this issue from geany/geany-plugins Jan 20, 2021
@atarax42
Copy link
Author

atarax42 commented Jan 20, 2021

Aha. Thanks. Would reduce confusion and improve productivity, if both panes had the same functionality, though.

@elextr
Copy link
Member

elextr commented Jan 20, 2021

Its not that there is no understanding of the potential benefits, but ...

Its not so simple as saying it, there have been several attempts to make it happen.

But they require a lot of work because lots of the existing code simply wasn't written to allow for more than one pane (which is why much of it doesn't work in the second pane) or they have limitations (like the current plugin) or they have performance problems (like the switch pane implementation).

So none has been good enough to displace the limited existing limited plugin. Perhaps it should be made read-only and documented as such, but nobody has felt its worth cutting off the limited functionality it has.

Probably the existing plugin could use better documentation though. Actually any at all its not mentioned in the manual.

Pull requests are welcome.

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