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

Rename buffer type name to avoid compiler confusion (#78) #79

Closed
wants to merge 1 commit into from

Conversation

bram85
Copy link

@bram85 bram85 commented Jul 28, 2021

The variable name is the same as the type, causing the wrong value to
be returned from the buffer_create() function. The buffer_create()
caller would see buffer size 0, causing trouble when growing the
buffer when reading data ("middleware out of memory").

This addresses issue #78 which shows this error message in a Termux environment.

The variable name is the same as the type, causing the wrong value to
be returned from the buffer_create() function. The buffer_create()
caller would see buffer size 0, causing trouble when growing the
buffer when reading data ("middleware out of memory").

This addresses issue magit#78 which shows this error message in a Termux environment.
@omecamtiv
Copy link

omecamtiv commented Aug 13, 2021

Thanks @bram85 your fix also fixed a similar issue faced by me while using magit/forge in a Termux environment. Thanks again. @skeeto please look into this and merge this pull request, as many Termux users are facing the issue.

@nickanderson
Copy link

This fixed an issue I was having with org-roam.

@zbillman
Copy link

This also fixed my issues with org-roam in termux.

@hemanta212
Copy link

My emacs setup with magit-forge and org-roam is finally working now in termux. Many thanks to the author of this patch and this repository. Hopefully, this will be merged soon.

@tarsius
Copy link
Member

tarsius commented Sep 16, 2022

Please check whether 3747260, which was applied in February to fix #91, also fixes #78, making this pull-request unnecessary.

@tarsius tarsius added the legacy-sqlite Issues concerning the legacy sqlite back-end label Sep 17, 2022
@bram85
Copy link
Author

bram85 commented Oct 31, 2022

@tarsius Yes, looks like your fork (with the commit referenced) works OK on Termux.

@bram85 bram85 closed this Oct 31, 2022
@tarsius
Copy link
Member

tarsius commented Nov 1, 2022

Thanks for getting back to me!

(It's not a fork, I am the new maintainer.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy-sqlite Issues concerning the legacy sqlite back-end
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants