Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Does it blank always, or only sometimes ("random")?
My guess is that this happens because the website takes a while to respond and i3bar decides to leave the field blank for that time. You could work around that in several ways.
That said I have no clue how i3blocks (not part of i3wm) interacts with i3bar. Is it possible to pipe a script directly to i3bar?
Does it blank always, or only sometimes ("random")?
My guess is that this happens because the website takes a while to respond and i3bar decides to leave the field blank for that time. You could work around that in several ways.
An interesting thought. I'll try a different url source
Originally Posted by ondoho View Post
Does it blank always, or only sometimes ("random")?
My guess is that this happens because the website takes a while to respond and i3bar decides to leave the field blank for that time. You could work around that in several ways.
That seems to have done the job. No more blanking. Oddly, a site "failure" didn't even cross my mind.
It's amazing how these tiny tiny issues can prey on your mind. I feel free again
Irony of ironies. ipinfo.io works really well but there is a limit on free use of the API. It worked until it didn't.
I think I may abandon my obsession with having the country of my VPN IP displayed by i3blocks. I'll simply check using CLI when I feel it's necessary to be certain that I'm connected "in" a specific country.
Actually, I didn't suggest to change the site at all.
You could try to rewrite the script in a way that "empty waiting" doesn't happen.
No. You didn't suggest this. I simply hadn't considered that the site might be causing the issue. The issue went away once I changed the site. It created a new issue though
I will investigate rewriting my curl request so that the "empty waiting" doesn't occur.
I will investigate rewriting my curl request so that the "empty waiting" doesn't occur.
I didn't say that either.
Please be precise when quoting people.
I said you could try to rewrite the script.
You cannot tell the website to go faster, it's not in your or your computer's power.
But you can, e.g.: save the value you get from the site to a file, and update the file only when the value changes, and make i3blocks look at the file and not curl's output at all. Just an idea off the top of my head.
But there should be a simpler solution; I suspect soemthing is amiss in the interaction between
your script <=> i3blocks <=> i3bar
You have not given much information on that.
I'm lost. You are quoting me above. Is it that I used your words -- "empty waiting" -- that causes confusion?
Quote:
Originally Posted by esteeven View Post
I will investigate rewriting my curl request so that the "empty waiting" doesn't occur.
This is how I phrased what I intend to do. It exposes my limited experience with scripting but this is how I described my plan of action.
Quote:
But there should be a simpler solution; I suspect soemthing is amiss in the interaction between
your script <=> i3blocks <=> i3bar
You have not given much information on that.
Let me quote myself:
Quote:
No idea. Yet.
Cheers
You are undoubtedly correct when you say that there is something amiss.
Quote:
I suspect soemthing is amiss in the interaction between
your script <=> i3blocks <=> i3bar
You have not given much information on that.
That's what I have no idea about. I have never delved into this because I have never needed to.
Well, in a way you're right; it's possible that curl has some option that would avoid long waits.
But more important is how i3blocks & i3bar work together and how you integrated that script in the first place.
You aren't really sharing any details here, that makes it kinda impossible to find a solution together.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.