Search
306 results for “YesJustWolf”
-
I run on four different #bash implementations: #macos. #ubuntu on a standalone machine. Ubuntu under #wsl. #gitbash for Windows. #neovim works fine under all but the last, which starts up with the error message C:\Program Files \Git\usr\bin\bash.exe is not executable. In the actual message the quotes look appropriate. #Vim runs fine on all four.
-
@hare_ware Putting in my vote for #HelixEditor. I've used everything you've mentioned. I'm a #Vim expert (I've even made videos). #PyCharm is what we use at work and has been a favorite (with Vim bindings #IdeaVim) forever; but I'm all in on Helix. This is a datapoint for you, not any kind of coercion. Give it a chance, compare, decide if it gives you what you need.
-
@b0rk I am absolutely not telling you what to do. I'm giving you a datapoint. I am a #Vim / #NeoVim expert. I have used Vim for ... hmm, maybe it's decades. Not sure. I use Vim key-bindings everywhere that I can. I have given talks and made YouTube videos about Vim.
I’m always trying new things. For instance, #RustLang. One thing I thought I'd try is the #HelixEditor. For a lot of people, and you may well be one, Vim/NeoVim is the right choice. If it is, I won't try to convert you. But my experience so far with Helix has been so positive, that even after decades of Vim being my favorite, it has been replaced by Helix.
I still use Vim wherever that's the right choice, for instance remote machines I don't control. But editing actual code in Helix using that language's LSP and with tree-sitter is absolutely delightful. Even the fact that Helix isn't a “finished” editor doesn't dissuade me.
At work, #Python is our main language, and we all have PyCharm. I use the Vim bindings via #IdeaVim. I prefer Helix even to that.
So there's your datapoint. Maybe someone you know well and trust has an opinion that sheds more light on the two editors.
-
@art I’m a long time #Vim and #NeoVim user. In fact, I’ve given talks on them. I use Vim key-bindings everywhere I can; especially #IdeaVim in #PyCharm. I’ve been using #HelixEditor lately. The key-bindings come from Vim, but aren’t about playing code golf. They’re about being easy to use and remember. When you start a multi-key sequence, there is typically a menu that pops up showing you what the next key can be. The big difference, though, is that in Helix first you make a selection, and then you act on it.
Helix is easier to use than Vim/NeoVim. I’m just a Helix beginner especially compared to my skills in Vim. Helix is absolutely worth a try. If it’s Vim for you, then it’s Vim. But Helix might offer you something familiar but simpler.
-
I use #NeoVim, vi edit-mode in #bash, and #ideavim in #pycharm and #rustrover. In Bash, (once you hit Esc) you can edit in the line, or hit v to open up $EDITOR. But in the line, it’s really only vi, not Vim! So you can’t daw or ciw. Turns out I use the word text-object all the time! Very frustrating!
-
I’ve used all the major text editors. When not cross-platform, I do look at macOS apps, though I run all three OS choices day-to day. As I’ve said before, I mostly prefer #vim. I spend a lot of time in #pycharm using #ideavim. #helix is pretty good. I used it for three months and may give it a second chance. But I think the next thing to look at is #zed.
-
I love #vim. I use vim. I tried #helix. It was fine. I used it for three months. Back to vim. But I hear helix is getting better. Maybe it’s time to try it again.
Helix still won’t be available on remote systems. I use #ideavim in #pycharm. There won’t be an IdeaHelix. I hear helix is getting a #scheme. That would be a big deal.
-
I don’t always get to use Vim. Sometimes I have to use a Vim emulator, e.g. in PyCharm or Obsidian. Some Vim emulators are great. I love IdeaVim. But every one seems to have the same flaw. I always have to hit escape more than once (sometimes many times) to return to normal mode. I find it near the top of my frustration list. #vim #ideavim
-
I’ve been saying "no" to things so that I can (just) fit everything that’s left. Turns out, I should say "no" even more. The Japanese principle of "Hara Hachi Bu" #HaraHachiBu says leave even more space! Eat till you’re only 80% full. Only fill 80% of your available productive time with planned tasks, etc.
Learned this thought from "The #Productivity Show" (https://www.asianefficiency.com/podcasts/).
-
I have said before, I like to praise the things I like and find useful. I love #Obsidian. I use it every day. My use of it is very simple. Even though I’ve been using it for years, I don’t link all that much or use a ton of plugins. A tool I sometimes use on the underlying #Markdown files is #nvUltra. I love Obsidian’s model. I love the community. It’s great.
-
Still working on #AppleInChina #Apple and there really aren’t any good guys in this story.
-
Okay. So the #AppleInChina audiobook: the content is scintillating; the narration is absolutely terrible.
-
-
On #iOS, in the #HealthApp, setting your #Sleep schedule is weird. They **show** it to you like you’re setting the range of time you plan to sleep, i.e., go to sleep here, wake up here (the next morning). But that’s **not** the wake-up time for tomorrow! It’s the wake-up time for today! So the filled in part of the circle that it looks like you’re controlling? The sleep range? That’s **not** what you’re really setting, if i have this right (and I’m not sure that I do). You’re really controlling the other part: the "awake" range.
For me that means I need four total entries:
* Monday-Thursday: bed 8:30pm, wake 4:30am
* Friday: bed 10pm, wake 4:30am
* Saturday: bed 10pm, wake 7am
* Sunday: bed 8:30pm, wake 7am.It doesn’t even look right when I put "bed" first describing it here!
-
On #iOS, in the #HealthApp, setting your #Sleep schedule is weird. They **show** it to you like you’re setting the range of time you plan to sleep, i.e., go to sleep here, wake up here (the next morning). But that’s **not** the wake-up time for tomorrow! It’s the wake-up time for today! So the filled in part of the circle that it looks like you’re controlling? The sleep range? That’s **not** what you’re really setting, if i have this right (and I’m not sure that I do). You’re really controlling the other part: the "awake" range.
For me that means I need four total entries:
* Monday-Thursday: bed 8:30pm, wake 4:30am
* Friday: bed 10pm, wake 4:30am
* Saturday: bed 10pm, wake 7am
* Sunday: bed 8:30pm, wake 7am.It doesn’t even look right when I put "bed" first describing it here!
-
On #iOS, in the #HealthApp, setting your #Sleep schedule is weird. They **show** it to you like you’re setting the range of time you plan to sleep, i.e., go to sleep here, wake up here (the next morning). But that’s **not** the wake-up time for tomorrow! It’s the wake-up time for today! So the filled in part of the circle that it looks like you’re controlling? The sleep range? That’s **not** what you’re really setting, if i have this right (and I’m not sure that I do). You’re really controlling the other part: the "awake" range.
For me that means I need four total entries:
* Monday-Thursday: bed 8:30pm, wake 4:30am
* Friday: bed 10pm, wake 4:30am
* Saturday: bed 10pm, wake 7am
* Sunday: bed 8:30pm, wake 7am.It doesn’t even look right when I put "bed" first describing it here!
-
On #iOS, in the #HealthApp, setting your #Sleep schedule is weird. They **show** it to you like you’re setting the range of time you plan to sleep, i.e., go to sleep here, wake up here (the next morning). But that’s **not** the wake-up time for tomorrow! It’s the wake-up time for today! So the filled in part of the circle that it looks like you’re controlling? The sleep range? That’s **not** what you’re really setting, if i have this right (and I’m not sure that I do). You’re really controlling the other part: the "awake" range.
For me that means I need four total entries:
* Monday-Thursday: bed 8:30pm, wake 4:30am
* Friday: bed 10pm, wake 4:30am
* Saturday: bed 10pm, wake 7am
* Sunday: bed 8:30pm, wake 7am.It doesn’t even look right when I put "bed" first describing it here!
-
I talk a lot about #Measuring things (so one knows if one is doing the right amount of the right thing); but I don’t measure my own use of **all** apps and tools across all OSs! I have some general ideas (and I’ve often talked about how wrong general ideas often are).
I spend most of my time on #Windows (it’s my whole workday). My personal machine is a #Mac. I’ve mentioned before that I use everything everyday. My actual work is split between #CommandLine tools (building things), running the things we’ve built, and web-stuff like document creation, tickets, and the like.
My #TaskManagement software is Mac and iOS only: #Things from #CulteredCode.
I like my total setup; but it’s long past time to measure! Am I doing the right amount of the right things?
-
I talk a lot about #Measuring things (so one knows if one is doing the right amount of the right thing); but I don’t measure my own use of **all** apps and tools across all OSs! I have some general ideas (and I’ve often talked about how wrong general ideas often are).
I spend most of my time on #Windows (it’s my whole workday). My personal machine is a #Mac. I’ve mentioned before that I use everything everyday. My actual work is split between #CommandLine tools (building things), running the things we’ve built, and web-stuff like document creation, tickets, and the like.
My #TaskManagement software is Mac and iOS only: #Things from #CulteredCode.
I like my total setup; but it’s long past time to measure! Am I doing the right amount of the right things?
-
I talk a lot about #Measuring things (so one knows if one is doing the right amount of the right thing); but I don’t measure my own use of **all** apps and tools across all OSs! I have some general ideas (and I’ve often talked about how wrong general ideas often are).
I spend most of my time on #Windows (it’s my whole workday). My personal machine is a #Mac. I’ve mentioned before that I use everything everyday. My actual work is split between #CommandLine tools (building things), running the things we’ve built, and web-stuff like document creation, tickets, and the like.
My #TaskManagement software is Mac and iOS only: #Things from #CulteredCode.
I like my total setup; but it’s long past time to measure! Am I doing the right amount of the right things?
-
I hate when people talk over each other. It’s very distressing. My wife and our kids do it to each other. My wife did it with her brother when he was alive. And Merlin Mann does it in podcasts. It’s almost unlistenable to me. #merlinmann
-
I am #type2diabetic. I use a #dexcom #g7 #cgm. I have an #applewatch. When the sensor warms up (happens once per sensor, new sensor every ten days), the watch vibrates and shows an alert telling me so. That vibration is enough to wake me up. Even if I’m awake, it’s annoying. But for some sensors it will happen over and over and over again. It seems specific to a sensor, not the app. It is immensely frustrating.
-
I use #Git. A feature of Git I leverage heavily is #Worktree. I usually have at least four around at a time. For small tasks, sure, a simple branch and then switch back, but bigger things: a worktree.
Making a worktree is actually annoying for me: not just the upfront decisions about branches and start points and where to put the new directory (and also immediately `cd`ing there: but getting all the #submodules (submodules suck by the way), hooking up `.envrc` if you use #Direnv (and you should be), which should then set up your virtual environment and path and stuff. Clone isn’t quite as bad but has some of the same problems.
I do this so often, I wrote a script. It might be useful to others with this workflow. It’s opinionated, and therefore I could really use some feedback! What did I do right? What did I do that’s only right for me? What is totally missing?
The script is stand-alone, though you do need #UV. (You don’t even need Python! `uv` will transparently get you everything!) Just download this one Python file, and get it on your `$PATH`. If you want the additional `cd` behavior, then add the shell function, too as described in the `README`. Everything is tested. The tests are right there, too.
https://github.com/wolf/dotfiles/blob/main/git/dot-config/git/bin/make-worktree.py
The `README.md` is right next to it.
I **do** see one thing I’m missing: I need to provide a way to automatically copy in your custom stuff. I’ll add that today.
-
I use #Git. A feature of Git I leverage heavily is #Worktree. I usually have at least four around at a time. For small tasks, sure, a simple branch and then switch back, but bigger things: a worktree.
Making a worktree is actually annoying for me: not just the upfront decisions about branches and start points and where to put the new directory (and also immediately `cd`ing there: but getting all the #submodules (submodules suck by the way), hooking up `.envrc` if you use #Direnv (and you should be), which should then set up your virtual environment and path and stuff. Clone isn’t quite as bad but has some of the same problems.
I do this so often, I wrote a script. It might be useful to others with this workflow. It’s opinionated, and therefore I could really use some feedback! What did I do right? What did I do that’s only right for me? What is totally missing?
The script is stand-alone, though you do need #UV. (You don’t even need Python! `uv` will transparently get you everything!) Just download this one Python file, and get it on your `$PATH`. If you want the additional `cd` behavior, then add the shell function, too as described in the `README`. Everything is tested. The tests are right there, too.
https://github.com/wolf/dotfiles/blob/main/git/dot-config/git/bin/make-worktree.py
The `README.md` is right next to it.
I **do** see one thing I’m missing: I need to provide a way to automatically copy in your custom stuff. I’ll add that today.
-
I use #Git. A feature of Git I leverage heavily is #Worktree. I usually have at least four around at a time. For small tasks, sure, a simple branch and then switch back, but bigger things: a worktree.
Making a worktree is actually annoying for me: not just the upfront decisions about branches and start points and where to put the new directory (and also immediately `cd`ing there: but getting all the #submodules (submodules suck by the way), hooking up `.envrc` if you use #Direnv (and you should be), which should then set up your virtual environment and path and stuff. Clone isn’t quite as bad but has some of the same problems.
I do this so often, I wrote a script. It might be useful to others with this workflow. It’s opinionated, and therefore I could really use some feedback! What did I do right? What did I do that’s only right for me? What is totally missing?
The script is stand-alone, though you do need #UV. (You don’t even need Python! `uv` will transparently get you everything!) Just download this one Python file, and get it on your `$PATH`. If you want the additional `cd` behavior, then add the shell function, too as described in the `README`. Everything is tested. The tests are right there, too.
https://github.com/wolf/dotfiles/blob/main/git/dot-config/git/bin/make-worktree.py
The `README.md` is right next to it.
I **do** see one thing I’m missing: I need to provide a way to automatically copy in your custom stuff. I’ll add that today.