@freemo Yeah he did seem to turn quickly. As a critique of the interaction, maybe this set him off, you seem to be implying he's being PA, whereas I *think* you were saying you appreciated that he wasn't being PA? I'm used to your style of communication, and I am still not sure.
"You are welcome. Best way to end a conversation you have nothing further to add to is simply by not speaking. Comes across a little passive aggressive otherwise."
@LouisIngenthron @freemo Whether or not it is in fact faster or less error prone I have no clue, but that corollary doesn't appear to true, it was apparently designed to alternate left and right hands so the first typewriters didn't jam. The "slow typists down" thing seems to be an often repeated myth.
@adx vertico-directory for the directory navigation.
@uncomfyhalomacro make sure you have native json enabled in your emacs build. I use eglot myself but I didn’t think it was faster.
@uncomfyhalomacro to start? It’s usually ~0.4s on my Linux box. ~0.2s console. Deps on file cache warmness as well. It can be a few secs right after a boot. Fairly beefy machine.
@uncomfyhalomacro Emacs. I have 149 use-package configurations. Of those 35 just customize built-in packages. So probably about 114 "plugins".
@debacle @Sdowney @uncomfyhalomacro
This seems oddly restrictive. Why would you do that?
@mph You will still get multiple matches per file, it's just not grouped. I haven't actually been able to use `-- -l` and get any results at all. Not sure if that's a bug or not.
@mph
You can turn off the grouping via a configuration.
`(consult-customize consult-ripgrep :group nil)`
If you wrap consult-ripgrep or any consult command for that matter with your own command, you can do the above with your new command instead and the group setting should be applied to just it instead of consult-ripgrep.
I do this for my wrapper around consult-notes-search-in-all-notes, a function provided by consult-notes package, which you might want to check out, lets you search multiple directories.
Hmm, I WAS talking about danger, specifically the threat of violence. The quote didn't really specify what caused that fear, so I didn't think it was true in this case.
I agree that some things that might get you scared aren't a reason to restrict someone else's freedom, but there are things that can get you scared that should. So the original quote just isn't true in all cases, It sounds good but it shaves a few too many corners.
It seems freedom from the threat of violence is included as a natural right (did some research), which makes sense to me. I you saying you don't think that is a natural right?
You CAN kind of wing it, if you are in charge of the API, e.g:
<code>
let handle = create_window(WindowConfig {
width: 500,
z_position: 2,
autoclose: AutoclosePolicy::Enable,
..Default::default()
});
</code>
@freemo Aren't you violating my natural right to freewill and choice by coercing me to run via the fear of potential violence? This seems analogous to fraud, where the violation of one's rights isn't as obvious and getting e.g. bludgeoned. But it's still a violation.
@freemo I dunno causing someone intentional fear is not a protected right. There are specific laws against that kind of abuse.
@peterdrake I guess you mean reflection? Yeah, they do that. I had one attack my car's right (and only the right!) side car mirror almost continuously, had to cover it up for a week just to prevent damage, little guy forgot about it after that.
@Floyd Well, well, well.... What do we have here?
Old software developer. C++ developer by day, Rust for fun. Linux guy. Hacking on the intersection of #computervision and #neuroscience in my spare time. Fan of #SpaceX, but Elon, not so much.
*** NOTICE ***
I've been getting follows from some fairly dubious accounts, so I'm going to have to approve follows from now on. If you want to be approved, the bar is low, have some followers or a profile that checks out. Be patient, I may not check that often.
#rust #rustlang #emacs #elisp #cplusplus #i3wm #linux #embedded
#space #asciidoc #whisky #bebop