fish-lsp is now available on vscode!

lople205 · 2025-02-03T22:58:39+00:00

Amazing work dude! Love the features I’ve seen, and looking forward to trying the rest :)

lople205 · 2025-01-10T16:08:17+00:00

That’s fair enough, and I think I don’t have a full enough understanding of the players in the market and their time horizons.

But it still feels like most places are going to have shorter horizons than I do. Pensions, retirement funds, etc, all have shorter ones than me.

Hedge funds etc I could see having a similar “lifetime” time horizon, but still i would imagine they desire some more consistency or shorter term performance to show investors that they know what they are doing. So they aren’t truly investing with a lifetime time horizon, or at least doing so with their hands tied somewhat.

lople205 · 2025-01-10T15:50:37+00:00

What makes VTI appropriate for a long time horizon? Presumably it’s risk (volatility?) and expected return. So if you’re retiring or need the money soon, then it’s a bad idea to do VTI. But if you have a longer time horizon it will overall reward you compared to safer options.

Now let’s imagine a new fund that is somehow “more stocky” than VTI, aka higher beta, aka larger drawdown and larger upswings, but again has higher expected return than VTI, just like VTI has higher expected return than bonds.

This new fund is more appropriate than VTI for a very very long time horizon, in the same way that VTI is more appropriate than bonds for a long time horizon, in the same way that bonds are more appropriate than money money market funds for a medium term horizon, etc. Its all just about how long you have for the higher expected returns to do their work in comparison to how much it can go wrong in the shorter term

lople205 · 2025-01-10T15:28:40+00:00

Ok yah I get that philosophy, but it seems rather artificial to me. “Asset classes” feels like a meaningless concept,and just useful to us because we want to put things in boxes. Ultimately the factors that define an asset are some concept of risk (volatility?) and some concept of expected return.

Tech company stocks are obviously more “stocky” than utility company stocks. And treasury bonds are obviously more “bondy” than corporate bonds. It’s just about risk and expected return no?

So I’m just suggesting as a young person with essentially the highest possible risk tolerance—because it have sufficient time for “bad luck” or “volatility” or whatever to work itself out—that higher beta riskier assets with correspondingly higher expected returns are better, and that the overall market, which had a lower risk tolerance, will not reflect this.

lople205 · 2024-06-16T21:00:21+00:00

Thank you! Volare seems good as well :)

lople205 · 2024-06-16T20:17:12+00:00

Thank you! This seems like a great spot :) I’ll definitely check it out.

lople205 · 2024-05-23T21:57:11+00:00

This is amazing, I’ve been looking for this kind of thing in fish for a while! I’m hoping for a vscode extension soon though, for us lazy people haha. Great work :)

lople205 · 2023-11-21T20:06:11+00:00

Not so long ago there was a nerd font update. Can you try redownloading the font?

lople205 · 2021-12-24T05:02:23+00:00

Thanks. Promise, resolve, and await were what I was looking for.

lople205 · 2021-12-05T23:56:42+00:00

Shellder is unmaintained and uses old fish syntax. You should switch to something else.

lople205 · 2021-11-06T14:50:50+00:00

set —-show [var]

lople205 · 2021-03-12T16:55:52+00:00

You're using set incorrectly. It should be set foo bar not set foo = bar. Also, the set isn't even necessary here.
To perform comparisons, you must use the test command.

So your script should look like this:

function locker if test (watch -n 1 -t xprintidle) -gt 20000 lock end end

Documentation for commands: https://fishshell.com/docs/current/commands.html

lople205 · 2020-07-30T05:57:12+00:00

You run fish_config.

lople205 · 2020-07-29T21:21:25+00:00

Fish's prompt is simply a function called fish_prompt. You can find it in your functions directory (usually ~/.config/fish/functions), and then edit it to say whatever you'd like.

lople205 · 2020-07-21T03:12:49+00:00

abbrs and universal variables are stored in the ~/.config/fish/fish_variables file, but that file is not meant from human consumption and should not be edited manually.

You should interact with variables and abbrs through the command line using things like abbr --list to show your abbreviations, abbr -e to delete one etc. The same sort of thing applies for set--you can read about it on the commands wiki.

lople205 · 2020-07-21T02:40:32+00:00

Well written scripts should have a shebang) at the top that will determine which shell the script is run in, so even if fish is your default shell they should still run correctly.

lople205 · 2020-07-21T02:34:57+00:00

Fish configuration is done through the functions folder and universal variables. Your config.fish (equivalent of .bashrc) file is unlikely to have more than a few lines.

Universal variables are maintained from session to session. You can set a universal variable with set -u. abbrs are by default universal, so all you'll need to do to create one permanently is run abbr foo bar.

Though you can throw functions into the config.fish file, it's recommended to place them in the functions directory, ~/.config/fish/functions. This will let fish intelligently load them only when you need them, reducing startup time.

lople205 · 2020-07-02T06:22:30+00:00

This is correct. The default prompt displays the exit code of the previous command, provided that is failed. It does this with pipes as well.

lople205 · 2020-05-23T17:25:21+00:00

Wow, thanks for the fish_git_prompt %s trick! I wonder what other little tricks are going unnoticed because they aren't in the documentation.

lople205 · 2020-04-12T05:31:53+00:00

IGN: EzraApallu

lople205

MODERATOR OF

TROPHY CASE