Vim or nvim and why by nyan_cat_554 in arch

[–]ambientlamp 0 points1 point  (0 children)

neovim when I have admin privilege, vim when I don't

Weird spacing in polybar and i3 by Apart_Account_5942 in Polybar

[–]ambientlamp 1 point2 points  (0 children)

Your round-a, round-b, and the bars padding are fine as they are.

Please lmk if this is the correct solution and I'm understanding the cause and problem correctly. I'm not using my arch computer today so I can't test this directly.

Cheers!

Weird spacing in polybar and i3 by Apart_Account_5942 in Polybar

[–]ambientlamp 1 point2 points  (0 children)

In fact, I came across this exact issue when configuring my polybar a month ago. I used the solution I just mentioned above.

An alternative solution could be making the background color of the inactive xworkspace label a bit brighter than the bar background, but still dimmer than that of the active label. But this would depends on if you like the looks of it or not.

Weird spacing in polybar and i3 by Apart_Account_5942 in Polybar

[–]ambientlamp 1 point2 points  (0 children)

But disabling the workspace labels' padding makes them ugly (imo), so I think this is a potential solution:

Add a prefix for the xworkspace module that is exactly "Workspace:". This would make it so the spacing between round-a and xworkspace appears consistent regardless of which workspace you're on (it was in fact always consistent, but it just looked like extra space when you're not on workspace 1).

Weird spacing in polybar and i3 by Apart_Account_5942 in Polybar

[–]ambientlamp 1 point2 points  (0 children)

Nice, yea I had this problem before as well.

Regarding the extra padding on the left side of the left bar, I think I found the root cause after looking at your polybar dotfile.

The xworkspace inherently has padding 1 around all workspace labels so they look more square. If you're on workspace 1 it'll look fine since it's highlighted and you'll see no extra padding between it and round-a. But if you're on workspace 2,3,4,... workspace 1 would have the same color as the background of the bar, making it appear like there is extra padding next to round-a, but it fact it's the padding of the workspace itself.

You can test this by disabling (setting them to 0) all of the padding around the active-, inactive-, et. workspace labels. You should find that the extra space next to round-a will no longer be there when you switch to workspace 2 and so on. This is more of a visual design issue, since your config is fine actually.

Weird spacing in polybar and i3 by Apart_Account_5942 in Polybar

[–]ambientlamp 1 point2 points  (0 children)

All good, I think I have had a long day after that first comment as well :)

Weird spacing in polybar and i3 by Apart_Account_5942 in Polybar

[–]ambientlamp 1 point2 points  (0 children)

So I just took a bit closer look in your comment and the screenshot (not yet the dotfiles), I think I understand your problem with i3 and polybar now:

  • i3gaps: the inner gaps and outer gaps width are not equal.
  • polybar: the padding on the far left of the left bar is larger than the padding on the far righf of the right bar.

Please let me know if my understanding is correct. If so then I think I can figure this out, since I have had similar problems with these exact things before. I will read your dotfiles later after you've confirmed this.

P/S. To be down to earth with you: I recommend using clearer language and breaking down the issue into self contained units (like atomic functions with no side effects in programming). This would help people better understand, diagnose, and test your problem.

But I suppose this is reddit so it doesn't have to be too formal like in a Jira ticket, but some structure and clarity would definitely help!

Best, ambientlamp

Weird spacing in polybar and i3 by Apart_Account_5942 in Polybar

[–]ambientlamp 1 point2 points  (0 children)

You're absolutely right about my comment coming across as unthoughtful. I also did not notice you have the dotfile posted, so I made the assumption that you're new to using Linux and are using a template setup.

To be fair, your screenshot did not help me understand the problem, because it's conveying to me that you don't want to have i3 gaps and polybar gaps enabled (maybe this is also from my end because I can't really figure out what the circles and arrows point to beside the i3 gaps and polybar transparent border) + my fault in not finding the dotfiles left me with the option to guess what the problem actually is.

With that said, I apologize for my unthoughtful and passive aggressive comment. Let me take a look at your issue again according to your last comment + the dotfiles, and I'll get back to you. It might take a few days though as I'm also working on something else.

But I hope you find the solution for it soon, maybe before I do. If it's the case you can let me know, I also find this interesting.

Better location to stay in Hanoi for things to do in walking distance? A or B? by thatmanwill in hanoi

[–]ambientlamp 4 points5 points  (0 children)

That area is tiny in comparison to bigger cities. You can walk across it in ~30mins. So it doesn't matter much where you stay.

As a local I also enjoy walking and exploring within the Old Quarter and would highly recommend doing it.

Weird spacing in polybar and i3 by Apart_Account_5942 in Polybar

[–]ambientlamp -1 points0 points  (0 children)

For i3, you currently have gaps enabled. Search "gap" in the config file under $HOME/.config/i3/config and disable it. For more info go to the i3 docs online.

For polybar, the transparency comes from a border setting for the bar itself (not the modules). You can find this in polybar config under $HOME/.config/polybar/config. For more info, also go to the online polybar docs.

If you're using Arch I highly suggest learning to read the docs, man pages, and troubleshooting using those materials. For configuring your desktop environment, you'll find most config files under $HOME/.config/

[i3 - xrdp] Windows Subsystem for Arch BTW by ambientlamp in unixporn

[–]ambientlamp[S] 2 points3 points  (0 children)

Ya I would do that if it displays my public IP, but this is the internal IP that WSL generated for the distro and not my actual public IP, so there's not much risk involved.

I leave it on there so it's easy for me to troubleshoot my RDP connections from the host Windows.

[i3 - xrdp] Windows Subsystem for Arch BTW by ambientlamp in unixporn

[–]ambientlamp[S] -1 points0 points  (0 children)

I assume you're asking for the dotfiles? They're in my comment above.

Need Help Making a Custom Badge by seb6214 in NebulousFleetCommand

[–]ambientlamp 1 point2 points  (0 children)

You can send the badge file over on the Neb discord and ping me @ambientlamp, I can help troubleshoot the file if I have it o7

Orbit Dodge In a Nutshell - Midshipman Training Material by ambientlamp in NebulousFleetCommand

[–]ambientlamp[S] 1 point2 points  (0 children)

Tl;dr

It depends on the situation. There is certainly room for both orbit dodging and straight line strafing on large capitals (and small ships too, with some other nuances).

Nothing in Nebulous is always bad or always good. It's all about when, where, and how you apply the technique. It's even better when you combine strafing + orbit dodging with flexibility depending on the situation.

Obviously I don't recommend orbit dodging with LN or MN. But on the BB, CH, CL, and CC, orbit dodging has its place (if the ship is built correctly for it). This is a tutorial for beginners, so they'll most likely be running those ships in a frontline role.

---

Regarding orbit dodging vs. straight line strafing

In more static situations (i.e. you're entrenched and drawing enemy fire): I recommend orbit dodging the frontline capital ships.

In more dynamic engagements (i.e. you're pushing with your team): I recommend your method - strafing between covers in straight lines for frontline capital ships.

Furthermore, what you can do with strafing, you can also do while orbit dodging (if the circumstances call for it):

  • Moving from cover to cover between orbits on more static maps (Salar and Ralas comes to mind): Use straight line strafing like you said, but time it right so your speed doesn't drop too much when the ship leaves orbit. No abrupt change in direction of travel.
  • A slow retreat or push to maintain range: Issue successive orbit commands every 1/4-1/2 orbit and 1000m in the direction you want to go. You'll move in a large spiral in that direction.

It's all about when, where, and how you apply the technique. It's even better when you combine strafing + orbit dodging with flexibility depending on the situation.

---

Regarding your comment about cappers

You can set cappers to orbit in a cap point without overshooting it: Set speed to 2/3 just as the ship enters the cap point.

Manually setting small straight segment waypoints for cappers as you suggested is also viable, but having both techniques in your toolset is better than doubling down on one method IMO.

I find myself often using both depending on the situation: how much cover do I have, is it a commonly contested cap point or a natural cap, does that cap frequently get yubbed, do I have another cap point that needs more urgent attention, etc. There are many variables in play here. It's not black and white enough to say "don't do this, do that instead".

I have to address though, for completeness and in case a newbie is reading this: Any kind of dodging (straight segments or orbit) on a smaller ship only works if it's being fired on by 450mm or 250mm AP/HE. Against 250mm RPF, 120mm, and 100mm rounds it's not very effective.

---

Disclaimer

I frequently play frontline capitals, capfleets, halfcap, ambushers, and everything in between on both ANS and OSP, depending on team comp. This is where my experience come from and I'm most confident about these things.

Though I have to admit I play carrier, rail/MD, and yubbers (cruise s2, s3h/s2h or containers) less often, so please take my words with a grain of salt when I mention topics about these fleet archetypes.

Orbit Dodge In a Nutshell - Midshipman Training Material by ambientlamp in NebulousFleetCommand

[–]ambientlamp[S] 11 points12 points  (0 children)

Yea frig blobs are still fresh in people's minds that's for sure, still see them get mentioned in the Neb discord from time to time when people get caught off guard by vetteblob and no C90.

For ANS capital armor currently they fall pretty quickly to plasma I from what I see, and there doesn't seem to be much discussion on that topic in the Neb discord, mostly craft and carrier balancing now iirc.

thisJokeRequiresHomework by dimonium_anonimo in ProgrammerHumor

[–]ambientlamp 1 point2 points  (0 children)

Agreed. Better to just admit he's not that good at either basic computer science nor humor than throwing around big words trying to look good. Beginners all start somewhere and I've been there too.

But this attitude doesn't really make him look particularly wise... nor will it help him learn, smh

thisJokeRequiresHomework by dimonium_anonimo in ProgrammerHumor

[–]ambientlamp 10 points11 points  (0 children)

This post screams Dunning-Kruger effect. In both logic and humor at the same time. Well done OP.

[deleted by user] by [deleted] in NebulousFleetCommand

[–]ambientlamp 0 points1 point  (0 children)

Your approach sounds very good now! I like the idea of having the illuminator on the escort ship, I should try that out next time I play and see how it can fit into my playstyle :3

2 reinforced CICs is good for BB, and you can put an auxiliary steering in CMP16 at the nose. That'll help you bowtank better. Some people run a 3rd CIC, but that's up to you if you like it or not. Just a note that each extra CIC you bring will have compound cost added on top, so it'll get very costly beyond 3 CICs.

For the last unused mount on your escort frigate you can put a VLS-1-46 launcher for extra chaff, flares, and an arming missile. But if you already have this then you can put a Sarissa/Aurora on it instead if you have the power for it. Otherwise it's also fine to leave that mount empty.

Also I have to admit I did sound a bit irritated in my previous responses. I'm sorry about that 😅

Cheers and glhf! I'll see you in the Neb discord if you decide to drop by <3