-
Notifications
You must be signed in to change notification settings - Fork 31
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
Question: How do you recommend disabling the default modeline? #62
Comments
With the same hooks, you can use |
Makes sense. Thanks for sharing that knowledge. Closing this issue. |
Should this be mentioned in the README somewhere? The reason I am suggesting this is because following the configuration recommendations in the README I ended up with two mode lines as shown above. I then went wondering how to disable the default mode line and came here. Does using nano-modeline imply that the user will know to |
You're right actually, it couldm be mentioned in the README. Do you want to make a PR? |
Sure, but now this got me thinking on why it doesn't disable the default modeline when you enable the IIRC I haven't had to do this with other mode line packages. Correct me if I am wrong here. |
I'm actually not sure so maybe it is safe to disable header or mode line depending on where the nano modeline is. Best would probably to have a custom settings telling nano-modeline to disable mode/header line when in use. |
Hi, thanks for the reply. Can you elaborate on why it is not safe? I don't think I am understanding that part. |
If you use nano-modeline as a replacement for the regular mode-line and if I set header-line to nil, then it might be problematic if you were using the header line. There are a few packages that use the header line for this or that (for example list packages) such that I don't know if it is safe to disable it. |
Hi,
How do you recommend disabling the default modeline?
This is what is in my config:
The text was updated successfully, but these errors were encountered: