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

Zettlr 1.4.2 does not show any file or root in the left menu #360

Closed
HuebraG opened this issue Oct 13, 2019 · 7 comments
Closed

Zettlr 1.4.2 does not show any file or root in the left menu #360

HuebraG opened this issue Oct 13, 2019 · 7 comments

Comments

@HuebraG
Copy link

HuebraG commented Oct 13, 2019

Description

When a root is open, no folder are shown. The last file is on the editor, but if I try to open another folder, nothing appears to change.
zettlrpb

Reproducing

Install or update to version 1.4.1 or 1.4.2

Expected behaviour

Show the menu with files and folders

Screenshots

Platform

  • OS: Windows
  • OS Version 7
  • Zettlr Version 1.4.2 and 1.4.1
  • Screen Resolution [only necessary if the bug is relating to the GUI]

Additional information

I can revert back to 1.3.0, and it works again.

@nathanlesage
Copy link
Member

Could it be that this issue is a duplicate of #343? Because Zettlr will simply show nothing if there is one root with more than 7 or 8 sub-levels.

@viaregio
Copy link

I don't think that this is a duplicate of #343. I have installed Zettlr 1.4.2 on two computers, one with macOS and one with Ubuntu. Opening the same directory under the two systems I get different results. Under Ubuntu I get the same behavior described in this issue. Under macOS I have no issue.

@viaregio
Copy link

Sorry I have to correct myself. I wasn't aware of the fact, that Zettlr keeps a list of previously opened folders. The in #355 suggested fix worked for me.

@nathanlesage
Copy link
Member

So it's a duplicate as there was a folder with more subfolders …?

@viaregio
Copy link

I can't speak for the creator of this issue, but my issue is a duplicate of #343.

@nathanlesage
Copy link
Member

Ah, just realised that, never mind 😄

@nathanlesage
Copy link
Member

Closing as the issue might be that duplicate …?

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