Error Reporting #12
Error Reporting #12
Conversation
|
I'm finally back from exams and holidays etc. and am working on this again. Along the way I lost track of how far this PR got however. Are you ready to merge or did you have more planned. My apologies for the long hiatus. |
|
I know it's been 4 years, but I'd like to get an update on this PR, haha. |
|
@periish, as far as I know, this project has been a bit abandoned. |
|
Ouch. Well, I opened an issue about it being abandoned. I was asking about the xcb error handling code, personally. I’d like to merge it into my own branch. |
|
If you do end up forking this and plan on maintaining it, I’d be interested in helping out with things! I had a bit of a clipboard branch in the works for quite some time that never saw the light of day
… On May 27, 2020, at 4:55 PM, periish ***@***.***> wrote:
Ouch. Well, I opened an issue about it being abandoned. I was asking about the xcb error handling code, personally. I’d like to merge it into my own branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC2K73PC5EJSUNVTZOYNV2LRTWR6NANCNFSM4CBEXW2A>.
|
|
Nice, that’s good to hear. My personal fork currently fixes a few things that gcc complains about, and updates it to use fuse3. I’d be happy to maintain it, as it’s a tool I quite like. |
|
I like it!
…Sent from my iPhone
On May 27, 2020, at 4:59 PM, periish ***@***.***> wrote:
Nice, that’s good to hear. My personal fork currently fixes a few things that gcc complains about, and updates it to use fuse3. I’d be happy to maintain it, as it’s a tool I quite like.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I’d be interested in seeing your clipboard branch. How does it handle the mess of the Xorg clipboards? |
|
It was able to set the clip I think? There were files $X11FS/clipboard and $X11FS/primary or something like that; it’s been forever since I poked at it. Should be still on my repo, but I’ll double check.
… On May 27, 2020, at 5:02 PM, periish ***@***.***> wrote:
I’d be interested in seeing your clipboard branch. How does it handle the mess of the Xorg clipboards?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC2K73LIUNMMBMX6TLGQC73RTWSZLANCNFSM4CBEXW2A>.
|
|
I put up a PR on your repo, don't pull it. It's just there for reference, take what you'd like from it for sure though and I'll futz with it when I'm settled in again. |
|
Yup, apologies this project has not been on my radar for a long time now. (I've been busy starting and abandoning other projects :^) ). More seriously though, I'm not against doing more work on it, but I'm in the middle of writing up my masters right now, so I certainly wouldn't expect to see any changes for the next month or so. @periish your fork sounds great, and if you're happy to maintain it that would be fantastic. I'm mildly surprised people are still using this, but I'm glad you find it useful. |
|
I’d be happy to maintain it, yeah. Sounds good! |
This PR will include a shift toward exhaustive error reporting using
syslog().It should not be merged until both @sdhand and @HalosGhost have signed off.
When complete, this PR will close #3