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 -full, making FullGeneration the default #485

Open
wants to merge 1 commit into
base: 3.6.x
Choose a base branch
from

Conversation

uli42
Copy link
Member

@uli42 uli42 commented Jul 11, 2017

Addresses #191

@sunweaver
Copy link
Member

making FullGeneration the default

Are you sure, we want this? From the man page of Xnest as quoted in #191, I get the impression that making nxagentFullGeneration the default could create a lot of extra round trips (as the full generation happens betweem local Xserver and nxagent Xserver)... Have you checked this with xtrace?

@uli42
Copy link
Member Author

uli42 commented Jul 12, 2017

I have not checked this. AFAIU this is only needed when you close all clients. Normally Xnest will stay alive and not close down the Display connection. With FullGeneration it will close it and build a new one and then await new clients.

I am unsure now if that case ever happens in nxagent. We have -reset/-noreset, -once and -full. And we have nxagent quitting when the last client disconnects. Must think through this, help appreciated.

In any case we need a FullGeneration at the startup. So this seems like the natural default.

@sunweaver
Copy link
Member

sunweaver commented Jul 12, 2017 via email

@uli42
Copy link
Member Author

uli42 commented Jul 12, 2017

I am aware of that code. But if I keep all that logic this patch does not make any sense, as I have to keep most of the code.

@sunweaver
Copy link
Member

@uli42: Where are we with this (#485)?

@uli42
Copy link
Member Author

uli42 commented Jul 17, 2017

Well, I must check if any benefit remains after doing it as proposed above. Also my initial bug report #191 does not seem appropriate anymore, I cannot trigger the described behaviour. Can you?

@sunweaver
Copy link
Member

@uli42: ping(?)

@uli42
Copy link
Member Author

uli42 commented Jul 23, 2018

Aehm, my last queytion was, if you can trigger the fullscreen behaviour described in #191. So I'd better ping you ;-)

@sunweaver
Copy link
Member

@uli42: No, I can't reproduce "-full" switching nxagent to full screen mode. Tested against i3wm and marco WM (from MATE).

@sunweaver
Copy link
Member

@uli42: You just updated the -full option in the man page. Is this PR obsolete? Shall -full stay?

@uli42
Copy link
Member Author

uli42 commented Dec 19, 2018

Well, I just added the text from xnest explaining what the switch should do. As long as we have it we should also include it in the manpage. I have not looked any further regarding this pr

@sunweaver
Copy link
Member

sunweaver commented Dec 19, 2018 via email

@sunweaver
Copy link
Member

sigh... I am sorry, but pr/drop-full-generation got forgotten meanwhile. It should still be merged, I guess. Please rebase. Thanks.

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