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

remove menu bar and switch to fullscreen as well #2

Closed
wants to merge 1 commit into from

Conversation

anarcat
Copy link

@anarcat anarcat commented Jan 26, 2015

this remembers the previous menu bar setting, but not the full screen
setting.

we therefore assume full screen mode is always off before turning on
darkroom, which may be inaccurate.

we do our best with fullscreen, yet it doesn't always seem to be enough, see:

http://www.emacswiki.org/emacs/FullScreen

... for more information. it may also be useful to consider more frame
parameters, see:

https://www.gnu.org/software/emacs/manual/html_node/elisp/Management-Parameters.html#Management-Parameters

for more ideas. "sticky" strikes me as a possibly good idea.

note that I already sent a similar patch by email before finding this git repository.

this remembers the previous menu bar setting, but not the full screen
setting.

we therefore assume full screen mode is always off before turning on
darkroom, which may be inaccurate.

we do our best with fullscreen, yet it doesn't always seem to be enough, see:

http://www.emacswiki.org/emacs/FullScreen

... for more information. it may also be useful to consider more frame
parameters, see:

https://www.gnu.org/software/emacs/manual/html_node/elisp/Management-Parameters.html#Management-Parameters

for more ideas. "sticky" strikes me as a possibly good idea.
@joaotavora
Copy link
Owner

First of all, thanks for bringing this in as a pull reuqest. I see you had already sent me a mail, but it slipped through my inbox. Sorry about that. I'll have a look.

@anarcat
Copy link
Author

anarcat commented Jan 26, 2015

thanks, and no trouble for the delay. this is not the same patch as what i sent by email, which had weird issues and didn't remember menubar settings.

@anarcat
Copy link
Author

anarcat commented Oct 13, 2015

ping?

@joaotavora
Copy link
Owner

I don't know...

(1) even if you save the initial state of those variables, aren't there cases where you don't to remove those two particular distractions?

(2) Most importantly, the things you are plotting to hide are frame-specific things, not buffer-specific things. So one buffer in darkroom-mode would be responsible for (dramatically) changing the look of every other buffer not in darkroom-mode. How would this work with darkroom-tentative-mode, for instance?

Because of this, I would add a darkroom-clean-frame-mode that removes the menu bar and fullscreens the frame. But this is only a very small saving over calling toggle-frame-fullscreen and menu-bar-mode manually, once per session, which is probably what most users are after.

@anarcat
Copy link
Author

anarcat commented Oct 13, 2015

well, maybe a different mode would be in order, but to respect POLA, i think frames and menus should be dealt with. It's a major distraction...

@joaotavora
Copy link
Owner

It's a major distraction...

I agree fully: I have my emacs fullscreened and menu-bar-less most of the time. I use toggle-frame-fullscreen once in a while to turn if off...

But another question is what should M-x darkroom-mode do to with them? What about M-x darkroom-tentative-mode. If the answer to both, after considering the implications, is "hmmm, nothing I guess", then there are, in my view, already commands in the Emacs core to control them, and darkroom.el doesn't need to add them.

@anarcat
Copy link
Author

anarcat commented Oct 17, 2015

i was hoping to have darkroom as an all-in-one solution, without forcing users to fiddle too much with their .emacs...

@joaotavora
Copy link
Owner

OK, but have you tried seeing the implications of the code you are proposing? In the current version a buffer can be in darkroom-mode and another buffer not in darkroom-mode. I can switch between those buffers happily, and if I hide the buffer in darkroom-mode it's like I've never activated it at all. In your code it doesn't happen and I suspect it would fail even more tests...

i was hoping to have darkroom as an all-in-one solution, without forcing users to fiddle too much with their .emacs...

Then write anarcatroom-mode based on darkroom-mode, I don't mind :-)

@anarcat
Copy link
Author

anarcat commented Nov 10, 2015

in rnkn/olivetti#6, i was pointed towards https://github.com/joostkremers/writeroom-mode which answers this requirement. thanks for the responses!

@joaotavora
Copy link
Owner

I take the opportunity to restate, from the rnkn/olivetti#6 discussion, that @rnkn made the same points I did here. I believe you will run into problems when you want some buffers in writeroom-mode and others not in writeroom-mode. Best of luck anyway.

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

Successfully merging this pull request may close these issues.

2 participants