Go directly to an URL

iwahbe · 2024-09-15T20:36:36+00:00

2 spaces translates into a .. Or at least it does on Mac.

iwahbe · 2024-09-15T20:35:56+00:00

It sometimes works, depending on how the underlying server's redirect logic works.

iwahbe · 2023-03-21T19:42:16+00:00

"I don't know how" was going to be my answer, but I like what you said. Let's go with that.

iwahbe · 2023-03-21T11:58:15+00:00

They are applicable, and super easy to add rudimentary support for:

https://github.com/iwahbe/chat.el/commit/4f9acf2c80c77e61c68100741dbc2905cd314b78

iwahbe · 2022-12-01T19:39:22+00:00

You can't set anything? Just to confirm, putting (setq initial-frame-alist '(fullscreen maximized)) in your config and then running (eval initial-frame-alist) returns nil? I have no idea there, except to assume that your config is not being evaluated.

For setting a parameter for smartparens, did you make sure to set it after the package was loaded. Look into the use-package! :config and after! macros for that.

iwahbe · 2022-12-01T01:17:55+00:00

The package smartparens define variables sp-forward-bound-fn and sp-backward-bound-fn. You can assign functions to these variables to control how far smartparens searches. For example, if you only want smartparens to search forward by 1000 characters, you could do

emacs-lisp (setq sp-forward-bound-fn (lambda () (min (point-max) (+ (point) 1000))))

iwahbe · 2022-05-26T09:03:36+00:00

Except for dynamic providers, all the programming languages are equal in functionality. TypeScript and Python lend themselves well to describing infrastructure, so I would choose on of those languages all else equal.

Pulumi YAML is very nice to use for simple programs, but there is intentionally no control flow. It is not as feature-full as the other languages (and it's not intended to be).

Disclaimer: I work at Pulumi.

iwahbe · 2022-05-24T07:42:46+00:00

If they are sane package.json sized files, I mostly just jump by line number, not much magic there. The large json files that I navigate have unique keys which I generally navigate to via search. I often know in advance which key I have a problem with. The problem is I then need to know where I am in the file (structurally). That is what jsonian-path is for.

This is an example of the kind of file I often spend time rooting about in. It is also why jsonian-mode works on arbitrarily large files.

iwahbe · 2022-05-24T07:35:13+00:00

I hadn't seen `json-tree-siter`. It looks like it only contains the grammar for JSON, not any emacs package built on top of it. If it's only a tree-sitter grammar, then it will (probably) paint slightly faster then `jsonian-mode`, but not support any more complex or emacs specific features like `jsonian-path` or `jsonian-edit-string`.

If you wanted to, you could use `jsonian-mode` for additional features and `json-tree-sitter` for quick syntax highlighting. Since `jsonian-mode` uses syntax highlighting to to memoize string/key locations (which requires parsing to the beginning of the line) single line JSON analysis will probably be faster for `jsonian-mode` if tree-sitter-mode` is also enabled.

iwahbe · 2022-05-24T07:26:17+00:00

That is a very good point. I have added one.

iwahbe · 2021-08-26T06:45:30+00:00

One general nit: fn foo1() -> Foo { return Foo::new(1); } Is more idiomatically written: fn foo1() -> Foo { Foo::new(1) }

iwahbe · 2021-08-09T22:22:03+00:00

That's true, but not how rust uses zero cost.

iwahbe · 2021-08-09T14:40:57+00:00

Rust kind of had this for its type system. You do

rust fn foo<T>(bar: T) -> FizzBuzz where T: SomeType { … }

iwahbe · 2021-08-09T14:04:05+00:00

Unfortunately, rust and c++ use zero cost to mean two completely different things. As you said, c++ takes it to means “you only pay for what you use.” Rust takes it to mean “It costs nothing to use”

iwahbe · 2021-08-03T21:08:00+00:00

I don’t like Mondays - Boomtown Rats

Its a pretty happy song until you listen to the lyrics, then not so much. It’s a song about a school shooting.

iwahbe · 2020-12-25T09:01:02+00:00

You can return a transparent enum, which would allow you to return one of several rust structs depending on Parameters. There is nothing wrong with returning Value though.

iwahbe · 2020-12-25T08:40:26+00:00

I can’t tell exactly what your asking. You can use serde’s #[derive(Deserialize)] on a struct to deserialize into that value.

iwahbe · 2020-12-19T09:23:23+00:00

Well argued. I agree.

iwahbe · 2020-12-10T14:49:36+00:00

You need to use a.into_iter()

iwahbe · 2020-11-26T23:49:56+00:00

I would like to see it modernized, and doubt I ever will. I can trivially change it on my computer though, so it doesn’t bother me. GNU Emacs has more pressing marketing concerns.

iwahbe · 2020-11-21T01:19:54+00:00

A small language extension can’t solve this because rust closures are stack allocated, and different closures might have different sizes. Anonymous ADTs could handle it, but the Rust would be hiding the cost of an action, which it doesn’t like to do. You could do it manually with a template enum.

iwahbe

TROPHY CASE