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

Reimplement eaf refactor with fix #14684

Conversation

dalanicolai
Copy link
Contributor

Thanks for merging the eaf update quickly @smile, but @lebensterben and I were still planning to make these little changes (see commit message).

This PR reimplements the refactor changes by @lebensterben but with his fix as
he suggested [here](syl20bnr#14681 (comment))
@@ -131,6 +131,7 @@
("-" . "insert_or_zoom_out")
("=" . "insert_or_zoom_in")
("0" . "insert_or_zoom_reset")
;; ("d" . "insert_or_dark_mode")
Copy link
Contributor Author

@dalanicolai dalanicolai Apr 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought I do keep it here (but commented out). It can be made working again with some modifications to the eaf package (the same modifications I made there before)

@dalanicolai
Copy link
Contributor Author

Ah, I see this PR consists of two commits now. I had created a PR but forgot to sync with develop first. So then I created a new PR (in a new branch) and just merged the fixes from this previous PR/branch. Is it easy for you to squash it/cherry pick? I have to look up again how to do that (this time when trying to rebase interactively, it asks me if I want to continue with a merge within the range). If I had had more time I would go sort it out, but I think for you this is easy (otherwise let me know of course).

@dalanicolai dalanicolai force-pushed the reimplement-eaf-refactor-with-fix branch 2 times, most recently from 5f0192c to 72aef58 Compare April 20, 2021 07:11
This PR reimplements the refactor changes by @lebensterben but with his fix as
he suggested [here](syl20bnr#14681 (comment))
@dalanicolai dalanicolai force-pushed the reimplement-eaf-refactor-with-fix branch from 72aef58 to 354ed12 Compare April 20, 2021 07:12
@lebensterben
Copy link
Collaborator

the real issue is not how you integrate it into spacemacs.

EAF is still in very early stage.

Just look at code like this. It just feels weird.

https://github.com/manateelazycat/emacs-application-framework/blob/b21efedaf78a2c41c36932c92884d930448b0516/eaf.el#L241

It needs some major refactors.

I spent much time trying to make the code short, fast, and idiomatic.

This eaf.el had >2000 lines.
That's a serious issue.

@lebensterben
Copy link
Collaborator

Or something like this

https://github.com/manateelazycat/emacs-application-framework/blob/b21efedaf78a2c41c36932c92884d930448b0516/eaf.el#L2594

He's using string like enum. But comparing string is much less efficient than comparing symbols or integers.

@dalanicolai
Copy link
Contributor Author

Yes I saw your bug-reports now at EAF, I have created two more myself too. But, despite the quality of the code, the browser and pdf-reader work (almost) flawlessly on my Fedora, and they are both really nice apps. Very good/helpful that you can advise them a little, but they did very nice work already of course. He already voted up your suggestions...

@dalanicolai
Copy link
Contributor Author

dalanicolai commented Apr 20, 2021

the real issue is not how you integrate it into spacemacs.

EAF is still in very early stage.

Just look at code like this. It just feels weird.

https://github.com/manateelazycat/emacs-application-framework/blob/b21efedaf78a2c41c36932c92884d930448b0516/eaf.el#L241

It needs some major refactors.

I spent much time trying to make the code short, fast, and idiomatic.

This eaf.el had >2000 lines.
That's a serious issue.

Haha, I am still only a hobby programmer. It is hard work for me to evaluate/judge this code... but of course I am trying to understand and learn from all feedback (as far as time allows)

@smile13241324
Copy link
Collaborator

Hmmm looks like you have made a rebase on the branch, I cannot properly squash or merge it.
Can you reproduce your changes on a fresh branch and make a new PR?

@smile13241324
Copy link
Collaborator

@dalanicolai is it ok for you to reproduce your changes on a new branch? If not I could also just copy them over and sign you in the commit message, if this is ok for you.

Just drop me a line.

@dalanicolai
Copy link
Contributor Author

@smile13241324 I have created the new PR (#14747) as requested, so this one can be closed.

@smile13241324
Copy link
Collaborator

New one is merged.

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.

3 participants