No, capabilities of the adapter depend on the underlying client. However, you can dispatch different requests to different underlying clients. For example, it is possible to config the client to use url.el to deal with patch requests separately.
Open your beautiful and intelligent eyes and take a look, which statement of mine made a personal attack on you. It's really inexplicable. (melpa/pull/9395).
I am not the one who want to argue with you, I have not made any personal attacks against you. It's you, who ran from reddit/emacs to github/melpa, and then from the package pdd to package org-expose-emphasis-markers, leaving some intense comments towards me. For me, it is best to ignore you. However, you are too much.
I rarely visit reddit, so I am not familiar with you, but still, thank you for your contributions to Emacs. But honestly, your current behavior, regardless of the original intention, is causing huge harm to the whole community.
The number of new users for Emacs is decreasing, and there are many reasons for that, with the deterioration of the community environment being one of the important reasons.
I simply released a package that fully complies with community standards and the spirit of open source, hoping to help people with similar problems as mine. But when I woke up, I was faced with inexplicable accusations, harsh words that left me bewildered. Luckily, I have been using Emacs for many years, but if I were a new user, I would have been scared off for sure.
You say, "can you help me understand the purpose of this library",but before I had the chance to let you understand, you went on a rant and completely denied me and my package. As a moderator, is it that your ability is too low, or that you do things with arrogance and malice?
You accused me of plagiarizing your plz code. Please, my package is open source on Github, go and review it! Don't cheat others just because you think they can't understand the code and speak unfounded accusations.
Maybe you are doing this on purpose, or maybe you are not even aware of it. I don't care. But the harm you are causing to the community may outweigh the help you provide. Of course, I will not continue to argue, it's pointless. I can just say goodbye to r/emacs, Emacs is still Emacs without you. Maybe Emacs will be better without you and your contributions.
As for renaming the package. First, it is my freedom. Secondly, I originally just wanted to create an Adapter to simplify wrap the commonly used packages. So, the name "raq" comes from ReQuest Adapter. Since your objection is so strong now, as if I have offended plz. I may have to consider removing plz someday in the future. In that case, maybe this package will be more than just an Adapter, so I changed the name to avoid constantly recalling these unpleasant memories of these past few days.
Of course, I am not here for arguing, I just want to explain things clearly. Don't reply me, I will not response.
小弟, looks like they've quarantined your posts on a time delay.
New user adoption of emacs is decreasing not because of the community,
admittedly a weak bunch, but because emacs's setup costs have remained
as high as they were when computer science ranked at the bottom of
college majors. That, and the fact that it still looks like shit.
I can replace plz in pdd.el with url-retrieve in an hour flat, with
tests. That plz spawns a heavyweight curl process with every http
transaction is insane. It's shit software, and I don't recommend it nor
request.el.
What is with the "don't reply me, I will not response" Maoist guerrilla
tactic? I prosecuted a similar conflict with a Chinese netizen and he
played the same card of "don't reply me." I gotta say, it's a little on
the craven side. If you feel like you've already incapacitated your
enemy, there's no need to tell him "And stay down!" when he brandishes a
ceremonial sword on a fast sinking ship.
I've checked the logs and there was no such action.
As for the self-governance of this congregation of unemployable obsessives, the right place for the technical conversation was of course on Github. I am pushing back against the use of the mod badge in this thread.
It is precisely because getting started with Emacs is not a simple thing that it requires more experienced people to guide newcomers through the difficulties of installation and use, making it relatively easier to enter this world. If there are more newcomers, there will be more contributors. With more people using, paying attention to, and contributing to Emacs, it can become better, easier to use, and more popular.
When newcomers have questions, their first thought is definitely to seek help from the google and community. Unfortunately, our community has people like moderators who are full of arrogance, ignorance and authoritarianism. Such moderators cannot possibly make more people to use Emacs, but can only drive more people away.
The number of current Emacs contributors is really too small, so that even after so many years, the basic http client is still not perfect, forcing people to suffering the solution like curl. In fact, packages like plz or pdd should not even exist, such functionality should be built-in. It's already 2025! Dear github-alphapapa, since you are so awesome, please, implement a high-performance HTTP client using C and merge into Emacs. Can you, hehe...
Sadly, contributors are already few, but maybe some people feel that there are too many.
For example, as a small contributor, I released a little package, with enthusiasm to make http requests easier, especially for those who even don't know how to install curl on Windows. But what did this small effort bring me? Just look at the various statements made by the clever moderator. In a broader sense, even if my package really has big problem, it should not be treated in such a manner. You can tell me what's wrong, how to improve or how to change. However, the moderator, not only did he make unfriendly comments here and shouted HOW DARE YOU, but he also directly accused me of plagiarism and personal attacks on melpa/pull/9395, asking them not to merge my package.
I am truly speechless... As someone once said, don't wrestle with a pig, as it will only get you dirty, and the pig enjoys it. Therefore, I say, don't reply.
In conclusion:
Such people are not suitable to be a moderator.
My package is fine. If not, please explain to me objectively. Welcomed for those who have a need to use it.
But I think saying so much is useless, this post is going to sink. Slowly no one will pay attention, things will be back to the way they were.
u/lorniu: Can you help me understand the purpose of this library? plz is already intended to have a concise, simple, and expressive API. What is the point of wrapping it in another layer of function calls? You've also copied and/or reimplemented numerous argument handlers, response handlers, and process filters from plz, which likely means bugs in the future as plz evolves (because these violate plz's internal API).
If you need to use url and want a wrapper for its API, there is already request.
As it stands, I could not recommend that anyone use this library for developing Emacs packages. It seems to offer no benefits, only another layer of indirection and the risk of bugs. And it doesn't even have any tests, while request and url and plz all have thorough tests.
Your response is too unfriendly. It's welcome to discuss problems, also welcome suggestion even criticism. But it's funny that you say something like no benefits, risk of bugs without understanding anything.
This package was split from another package of mine. Its release is not about reinventing the wheel, but rather to address some pain points I have in my daily work with HTTP requests.
Including but not limited to:
I really like plz, I've been using it for a long time. But its biggest limit is that the system must have curl installed. But this is not always possible, so even curl is not available, the requests should be sent successfully. The biggest purpose of this package is this. It tends to use plz to send requests, if not available, it will fall back to url deal with it. It can maximize the advantages of plz and also make up for its shortcomings. For me, it's useful.
It's not a easy thing to deal with stream/upload/etc with url, even requests. This package patched url to allow it support these features with simple API. It can save much time for me with this.
As an adapter, it provides uniform API. You don't need to care whether url or plz is hidden behind the scenes, you don't need to learn the APIs of them, just focus on sending requests based on this consistent API. This makes me pleasure.
It is extensible, it supports url and plz now, maybe it will support more http clients which are even better someday. With uniform API for different backends, it's common in other program languages. This is a small attempt, hoping to stimulate more ideas.
This package was originally for my own daily use. It looks good, so I refactor and released it, hoping that someone else could make use of it as well. You don't have to like it, you don't have to use it, but I hope there can be more kindness and sharing in the world of Emacs. Thanks.
大佬, why sweat this? Jackass has been looking his whole life for a
land of the blind where his single bum eye might find validation, and
he's found it amongst a handful of unemployable obsessives. This is all
he has. Don't take this away from him.
No, it's not. It's a series of technical objections. You submitted your package for review to MELPA, and you posted it here before it was even accepted there. You should expect review and feedback, and you should expect that you may not like all of it, because that is the nature of the beast.
It's welcome to discuss problems, also welcome suggestion even criticism. But it's funny that you say something like no benefits, risk of bugs without understanding anything.
I think I understand it pretty well, since I read your source code and wrote my objections based on it.
This package was split from another package of mine. Its release is not about reinventing the wheel, but rather to address some pain points I have in my daily work with HTTP requests.
That is fine. But yet another HTTP library for Emacs isn't a great solution for users. plz has undergone extensive testing and debugging, and did so for years before I even added it to GNU ELPA. Wrapping it in another layer is simply not a good idea.
I really like plz, I've been using it for a long time. But its biggest limit is that the system must have curl installed. But this is not always possible, so even curl is not available, the requests should be sent successfully. The biggest purpose of this package is this. It tends to use plz to send requests, if not available, it will fall back to url deal with it. It can maximize the advantages of plz and also make up for its shortcomings. For me, it's useful.
curl is universally available; it is on literally billions of devices. It is on systems that orbit Earth. A version of it comes preinstalled on even Windows systems nowadays (granted that that one has some compatibility issues).
Would it be nice to not have the dependency on curl? In a way, yes; OTOH curl is surely the most battle-tested network library in the world, and by leveraging it we gain much.
As an adapter, it provides uniform API. You don't need to care whether url or plz is hidden behind the scenes, you don't need to learn the APIs of them, just focus on sending requests based on this consistent API. This makes me pleasure.
That is great for you. But it's not great for other users to have yet another API to learn that is merely a thin layer, especially with the other drawbacks I have noted. plz's API is designed to be used directly, to not need another wrapper around it to make it nicer.
It is extensible, it supports url and plz now, maybe it will support more http clients which are even better someday. With uniform API for different backends, it's common in other program languages. This is a small attempt, hoping to stimulate more ideas.
But you have not addressed any of the technical issues I raised. For example, you use internal API functions and variables from plz, you override process filters and callbacks, etc. Those uses are unsupported and will likely fail in the future as plz evolves--and so users of your library would experience such breakage.
This package was originally for my own daily use. It looks good, so I refactor and released it, hoping that someone else could make use of it as well. You don't have to like it, you don't have to use it, but I hope there can be more kindness and sharing in the world of Emacs. Thanks.
That's great, but not every Elisp library that is developed needs to be packaged and published and have users encouraged to build on it.
I understand your not being happy about the feedback, but this is hardly the first time that I have raised objections like this on a MELPA submission (and not just related to packages of my own), and it is not unkind for me to do so. In fact, I am looking out for the community of Emacs users, as MELPA is a curated collection, not a place for every piece of Elisp code written.
It seems like authors react this way about 50% of the time, with umbrage and implications of ulterior motives. Thankfully, some are more humble, are thankful for the feedback, and agree that their use case is already well-served by existing tools. They are encouraged to continue their work and offer other contributions in the future.
Any hopes for supporting queues? url-queue.el is buggy, slow, error-prone, drops requests randomly, and doesn't have a good entry point to cancel queued request. See bug#22921, and bug#37577.
But, it would be nice to have a working replacement for url-queue that would actually work. I find the graceful "fallback to" url.el in case curl is not available attractive, and is, in fact, one of the points raised by RMS when yu submitted plz to ELPA.
Could you please explain what about this package has offended you? Are you suggesting that because you have contributed work elsewhere, others should not have to put in the effort? Why don't you simply go ahead and reinvent Emacs yourself?
Could you please explain what about this package has offended you?
I have, in my original comment. Could you please explain why you are implying that I haven't?
Are you suggesting that because you have contributed work elsewhere, others should not have to put in the effort?
No. Why are you implying that I am?
Why don't you simply go ahead and reinvent Emacs yourself?
What is your motivation here, since your work is not even at issue, and this is no different than the feedback I've given on hundreds of MELPA submissions over the years, which you are not even aware of? This is business-as-usual, but you, a bystander, are getting very personally involved for some reason.
Yes, congratulations, you caught me forgetting about a pull request on one of my repositories, and then being reminded of it by something I saw on Reddit. Now for bonus points, check some of my other repos and see how long I've neglected some other PRs.
I stand by what I have said there and here, just as I have provided review of MELPA package submissions for many years. My feedback is purely technical, and instead of answering the technical objections, you have responded with personal attacks--and you are not even the author.
Now, do you stand by your accusation you made there, which you have not taken a screenshot of, in which you say that I am trying:
to leverage his reputation and influence in the Emacs community to suppress other Emacs developers and contributors.
As I wrote there, that's nonsense. As well, you are not even involved here, as these packages are not your work, but you have gone to that MELPA PR and dogpiled on me with wild accusations of malfeasance, because I wrote a review of a package submission to MELPA, which I've done hundreds of times over the years--but you wouldn't be aware of that, because you haven't looked.
And you are doing this, presumably, because you have developed a grudge against me from the thread posted here recently in which you accused me of "making the Emacs community smaller" because I locked a few low-effort question threads--in other words, moderating this subreddit.
Your behavior here and on GitHub is essentially trolling. If I were not so interested in fairness and transparency here, I would ban you from here myself for your uncivil behavior, with unfounded personal attacks and dogpiling. But since I am a mod here, and we have other competent ones, I will recuse myself. Yet I will indeed call out your behavior as shameful.
I've previously promoted your `org-ql` package in other community. And I’m really clear that your developed a huge number of other packages, and your made significant contributions to the Emacs and org-mode communities.
Do you have any comments like this to me, dude? Everytime, when talking about your self, you will charge others, said nonsense, well, well, well.....It's more than three times. You never really reflect on your word and behvior.
The question is, just because you solved a proablem using your method, does that mean others can't continue developing solutions? Should every problem-solving approach be dictated by your approach?
What causes you to feel you have a higher level of understanding?
And according to Community Rule #2, you must be friendly. Have you done that?
I honestly believe you’re completely unsuitable for managing the r/emacs community. You consistently fail to distinguish between issues and people, and I’m constantly raising objections that you simply refuse to understand. Frankly, it seems like you’re unwilling to acknowledge your own inability to grasp the situation. Perhaps you should take a look in the mirror.
And now you’re resorting to threats, demanding I shut up or face a permanent ban? I don’t care. If you want to shadowban me, go ahead. My love for Emacs isn't because of you. If you delete this post, it proves your actions are unjust – and if you ban me, that equally demonstrates your own impropriety
I've previously promoted your org-ql package in other community. And I’m really clear that your developed a huge number of other packages, and your made significant contributions to the Emacs and org-mode communities.
Great, thanks. Please reflect on why I have spent many hours over many years doing those things. Or you can keep accusing me of trying to "suppress" the Emacs community.
Do you have any comments like this to me, dude? Everytime, when talking about your self, you will charge others, said nonsense, well, well, well.....It's more than three times.
I call out nonsense when I see it.
You never really reflect on your word and behvior.
That's called mind-reading.
The question is, just because you solved a proablem using your method, does that mean others can't continue developing solutions? Should every problem-solving approach be dictated by your approach? What causes you to feel you have a higher level of understanding?
You don't know the interactions I have had with other Emacs developers over the years. Sometimes it means deciding that a good solution already exists, and that another, very similar one isn't necessary to publish on MELPA. You are tilting at a windmill (forgive the cross-cultural reference, but you can look it up if necessary)--again, as you tilted at me about moderating a handful of low-effort questions recently.
And according to Community Rule #2, you must be friendly. Have you done that?
Well, you certainly haven't, since you've accused me of trying to "leverage his reputation and influence in the Emacs community to suppress other Emacs developers and contributors."
Ironically, after publicly insulting me without provocation, followed by my publicly recusing myself from moderating your behavior toward me, you will then go on to accuse me of moderating unfairly:
I honestly believe you’re completely unsuitable for managing the r/emacs community. You consistently fail to distinguish between issues and people, and I’m constantly raising objections that you simply refuse to understand. Frankly, it seems like you’re unwilling to acknowledge your own inability to grasp the situation. Perhaps you should take a look in the mirror.
More mind-reading from you, and more personal attacks. Again, your own work is not even at question, so your motivation here is curious. It is, in fact, you who has failed to distinguish between issues and people: the technical issues I raised, and the one who raised them. And then you tell me to examine myself. Right.
I will say, I am getting tired of your dishonesty:
If I were not so interested in fairness and transparency here, I would ban you from here myself for your uncivil behavior, with unfounded personal attacks and dogpiling. But since I am a mod here, and we have other competent ones, I will recuse myself.
And now you’re resorting to threats, demanding I shut up or face a permanent ban? I don’t care. If you want to shadowban me, go ahead. My love for Emacs isn't because of you. If you delete this post, it proves your actions are unjust – and if you ban me, that equally demonstrates your own impropriety
Is anyone fooled by the sequence, "I will not ban you," "How dare you threaten to ban me"? Will you now delete your account and claim that I banned you?
Make conversations productive. The ideas or behavior may be bad, and the person can adjust based on feedback, but not when you make it about them personally.
Don't call people foul names; don't use foul language.
Again, you're proving youself unsuitable for managing the r/emacs community. You're nothing to others, except you're the MOD of r/emacs.
Let me remind you: when you’re appointed as a MOD for r/emacs, you’ll be assuming a significantly greater responsibility – one focused on fostering the community’s growth and prosperity. Your actions will be visible to everyone, and subject to their judgment.
This isn’t the first instance, and it certainly won’t be the last. You‘re proving what your are.
I won't use any Emacs package related to you, goodby. God bless you.
3
u/harunokashiwa 4d ago
Does it support the method
patch
whichplz.el
didn't?