-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
Update breaks app appearance #82
Comments
I'm using 26.1 on High Sierra and it works fine for me. The code I'm using is:
|
@mclearc yeah, exactly @frankjonen sorry for inconvenience, I've updated the readme and added few words to caveats section to reflect required actions (52192f0). |
@mclearc not at all similar. This just darkens the title bar and sets the text to white somewhen after the application has already launched. This just skins the window. @d12frosted the workaround you're noting in the caveats to get the exact same behaviour, doesn't yield a similar result. It just darkens the title bar and leaves the text black. The behaviour that |
@frankjonen Ok, possibly that was a bad decision to remove this option. Sorry for that. I will look into it ASAP, but I doubt that it'll happen before the weekends. If someone wants to step in, you know, PRs are WARMLY welcome! 😸 |
Ok. It seems that Emacs 26.1 already has all the necessary stuff to make it working. As @frankjonen said, it's not documented (or at least, I could not find any relevant documentation). After some trial I've managed to make it working by adding following code to the beginning of my (add-to-list 'default-frame-alist '(undecorated . t))
(add-to-list 'default-frame-alist '(fullscreen . maximized)) @frankjonen and @CestDiego, could you please check if it works for you? 😸 If not, please checkout what other options are in |
It's a well-meaning setting (and one that I had commented on before). Unfortunately it leaves you with a gap where the title bar used to be and no way to grab on to the window to scale it up vertically. Probably could do it with an AppleScript (example on my Pastebin) but I have no idea how to trigger it from the init.el / spacemacs.el setup. Using normal installation. In Emacs Preferences I've searched high and low for anything remotely resembling title bar related stuff. Absolutely nothing. |
@frankjonen |
BTW, you didn't specify any configurations you are making in any of your comments. It would be super helpful if you said in the first comment that you tried setting |
Oh right. I sort of implied neither of them making a difference to the gapishness.
No |
@d12frosted as you can see in this github issue: https://github.com/koekeishiya/chunkwm/issues/265#issuecomment-394801114 This has problems with the chunkwm window manager. It would be better if we had the no-title-bar option back. Would this just be a revert on the commit that removed it? I'm not familiar with the quirks of this but I would love to help make this happen. |
Thanks for checking @frankjonen and @CestDiego
@CestDiego unfortunately no, as the patch behind the toggle has no sense on Since I don't use this option I didn't notice it before we've spent some time trying to understand what's wrong. Anyways, I'll try to take care of this issue during this week. |
Great to know. Thanks for the support.
On Wed, Jun 6, 2018, 1:55 AM Boris ***@***.***> wrote:
Thanks for checking @frankjonen <https://github.com/frankjonen> and
@CestDiego <https://github.com/CestDiego>
Would this just be a revert on the commit that removed it?
@CestDiego <https://github.com/CestDiego> unfortunately no, as the patch
behind the toggle has no sense on 26.1+. That patch was an experimental
hack until 26.1 comes out. Right now Emacs has a means of creating
undecorated frames, but it seems to behave differently. Quick look at
nsterm.m didn't help to understand me why.
Since I don't use this option I didn't notice it before we've spent some
time trying to understand what's wrong.
Anyways, I'll try to take care of this issue during this week.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADI540r2sOCHPi1rX3a61TZAk5GCEHmzks5t527AgaJpZM4UQtH3>
.
--
Diego Berrocal
http://diegoberrocal.com
|
I've tried adding several changes to |
Thanks for keeping us updated. Do you think there is a way to use the
previous emacs formula in the meantime
?
On Mon, Jun 11, 2018, 1:40 AM Boris ***@***.***> wrote:
I've tried adding several changes to nterm.m, but it didn't help.
Following the thread I've started on mailing list, gonna file a bug, cause
I don't know why it doesn't allow to resize even after the changes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADI548Qn0DkUcL8eVYPtFJjkTBbIki3Tks5t7gK3gaJpZM4UQtH3>
.
--
Diego Berrocal
http://diegoberrocal.com
|
Yes, I thought about providing |
Short update:
|
That works. Thanks. However I hope that we can eventually use emacs 26 T_T |
Haha. I understand. Though right now I can't promise fast resolution for this issue on Emacs 26.1. |
Good news everyone! I've pushed a patch that does borderless Emacs (fe4dc95). The option is called Please note, that I highly advice against using this option, instead use |
@d12frosted I get this: |
@d12frosted this is what I get:
|
Does it fail when you build without no-title-bar option?
On Tue, Jun 12, 2018 at 21:24 Diego Berrocal ***@***.***> wrote:
@d12frosted <https://github.com/d12frosted> this is what I get:
~
➜ brew install emacs-plus --with-no-titlebar
==> Installing emacs-plus from d12frosted/emacs-plus
==> Downloading https://raw.githubusercontent.com/d12frosted/homebrew-emacs-plus/master/patches/borderless-frame-on-macOS.patch
Already downloaded: /Users/dberrocal/Library/Caches/Homebrew/emacs-plus-frame.patch
==> Downloading https://gist.githubusercontent.com/aatxe/260261daf70865fbf1749095de9172c5/raw/214b50c62450be1cbee9f11cecba846dd66c7d06/patch-multicolor-font.diff
Already downloaded: /Users/dberrocal/Library/Caches/Homebrew/emacs-plus--patch-5af2587e986db70999d1a791fca58df027ccbabd75f45e4a2af1602c75511a8c.diff
==> Downloading https://lists.gnu.org/archive/html/emacs-devel/2018-02/txtshOHDg6PmW.txt
Already downloaded: /Users/dberrocal/Library/Caches/Homebrew/emacs-plus--patch-ba9d9555256f91409c4a7b233c36119514ba3d61f4acdb15d7d017db0fb9f00c.txt
==> Downloading https://lists.gnu.org/archive/html/emacs-devel/2018-02/txtzUNqW9dNDT.txt
Already downloaded: /Users/dberrocal/Library/Caches/Homebrew/emacs-plus--patch-500b437c3ed03e0ef1341b800919aa85cc9a9f13ecbaea8d5fc67bf74510317a.txt
==> Patching
==> Applying patch-multicolor-font.diff
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/src/macfont.m b/src/macfont.m
|index 0445628..c9082a5 100644
|--- a/src/macfont.m
|+++ b/src/macfont.m
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
Error: Failure while executing: patch -g 0 -f -p1 -i /private/tmp/emacs-plus--patch-20180612-18212-rrfvli/patch-multicolor-font.diff
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGNNiTunxsxN5txoxw4k0VuFEx1JfvOcks5t8AdegaJpZM4UQtH3>
.
--
Cheers,
Boris
|
It does not fail |
Ah, my apologises. I made a mistake in a formula that I pushed. Was creating patch and applying it on two different machines and didn't copy paste everything. I was planning also to add a test for this. |
Sounds good. I'm happy to test it again when you are ready.
On Tue, Jun 12, 2018, 3:23 PM Boris ***@***.***> wrote:
Ah, my apologises. I made a mistake in a formula that I pushed. Was
creating patch and applying it on two different machines and didn't copy
paste everything.
I was planning also to add a test for this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADI54-GrW-iU3pUxBhnLDe3AjdMUAbedks5t8BVCgaJpZM4UQtH3>
.
--
Diego Berrocal
http://diegoberrocal.com
|
Already
On Tue, Jun 12, 2018 at 22:30 Diego Berrocal <notifications@github.com>
wrote:
Sounds good. I'm happy to test it again when you are ready.
On Tue, Jun 12, 2018, 3:23 PM Boris ***@***.***> wrote:
> Ah, my apologises. I made a mistake in a formula that I pushed. Was
> creating patch and applying it on two different machines and didn't copy
> paste everything.
>
> I was planning also to add a test for this.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#82 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ADI54-GrW-iU3pUxBhnLDe3AjdMUAbedks5t8BVCgaJpZM4UQtH3
>
> .
>
--
Diego Berrocal
http://diegoberrocal.com
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGNNiRBP-_GQUln1oJ07Sa2pVsuXTLMWks5t8BbigaJpZM4UQtH3>
.
--
Cheers,
Boris
|
It works :D
On Tue, Jun 12, 2018 at 10:07 PM Boris ***@***.***> wrote:
Already
On Tue, Jun 12, 2018 at 22:30 Diego Berrocal ***@***.***>
wrote:
> Sounds good. I'm happy to test it again when you are ready.
>
> On Tue, Jun 12, 2018, 3:23 PM Boris ***@***.***> wrote:
>
> > Ah, my apologises. I made a mistake in a formula that I pushed. Was
> > creating patch and applying it on two different machines and didn't
copy
> > paste everything.
> >
> > I was planning also to add a test for this.
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <
>
#82 (comment)
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/ADI54-GrW-iU3pUxBhnLDe3AjdMUAbedks5t8BVCgaJpZM4UQtH3
> >
> > .
> >
> --
> Diego Berrocal
> http://diegoberrocal.com
>
> —
> You are receiving this because you were mentioned.
>
>
> Reply to this email directly, view it on GitHub
> <
#82 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AGNNiRBP-_GQUln1oJ07Sa2pVsuXTLMWks5t8BbigaJpZM4UQtH3
>
> .
>
--
Cheers,
Boris
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADI54xGx5ETcpvVLK3A9foecTeGwU-sXks5t8HPXgaJpZM4UQtH3>
.
--
Diego Berrocal
http://diegoberrocal.com
|
Glad to hear 😸 So I am closing this issue. If there is something wrong with current implementation, just let me know (either in this issue or fire new one). |
Failing for me with
This is with a completely fresh install of homebrew, fwiw. |
Please try without |
@d12frosted Hi Boris without the P.S. If I omit the |
Oh totally forgot about this. The non Thanks @d12frosted for coming through with this. |
@benjamin-rood nice! I haven't checked why @frankjonen 👌 thanks for checking 😸 P. S. I hope these fixes for macOS Mojave will be merged soon into master branch of Emacs. |
@benjamin-rood |
With the option to turn off the frame title bars gone we have to resort to specifying it in the
init.el
where it gets loaded AFTER the app has already launched, not at launch. This would be sort of acceptable if it would work at all but after some searching this part of Emacs 26 was never finished. All it does is turn off the title bar, leaving a bigass gap on the screen top area. Also this doesn't seem to be documented as people find this stuff out by accident it seems.Also I tried to fix it by stepping back one version and got this error message.
Is there some special trick to step back to working versions?
The text was updated successfully, but these errors were encountered: