Skip to content
This repository has been archived by the owner on Dec 6, 2022. It is now read-only.

ElasticTabstops only works on first view #23

Open
microcontroller opened this issue Jan 27, 2021 · 4 comments
Open

ElasticTabstops only works on first view #23

microcontroller opened this issue Jan 27, 2021 · 4 comments

Comments

@microcontroller
Copy link

Tested with 7.9 and 7.9.1 on Win10 x64. I just installed ElasticTabstops and immediately noticed this.

When I start up notepad++ with a tab-delimited file, the plugin makes everything look nicely aligned. The moment I switch to another file tab (even if I switch back) or reload the file, it reverts to the original un-aligned view. Disabling/re-enabling the plugin doesn't help. Newly opened files are also not aligned. If I "Move to new instance" or "Open in new instance" then I get the aligned view (at least initially) but "Move to other view" or "Clone to other view" don't.

@dail8859
Copy link
Owner

@microcontroller

Thanks for opening this issue. Sorry for the delay. Had to set up my dev machine again which I haven't gotten around to for a while. On other machines I have seen some odd behavior like this but currently can't reproduce it again.

Could you provide an exact set up of steps to reproduce this? Also your debug info (under the ? menu). Probably also your Elastic Tabstops settings (under Plugins > Elastic Tabstops > Settings)

@rekna1
Copy link

rekna1 commented Oct 25, 2021

I'm having the same problem, n++ 8.1.5, plugin version 1.3.1 (64bit).

When I move the view to another instance, it starts working. Even on new tabs.
I have default settings in ini

Maybe, plugin behaves differently when n++ opens with restored non saved files (n++ saves non saved files in a folder, reopens them at startup, without having to explicity save them or giving them names).

@andry81
Copy link

andry81 commented Oct 25, 2021

Just interesting, does it align if close and reopen the tab through the ctrl-w+ctrl-shift-t?

@rekna1
Copy link

rekna1 commented Oct 25, 2021

no it does not.

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

No branches or pull requests

4 participants