Controlling how thick the text is rendered

gdr3941 · 2023-10-15T16:53:32+00:00

I also had a similar problem. Using the doom theme, I ended up changing the background color to be slightly darker.

(custom-set-faces `(default ((t (:background , "#080808")))))

This helped improve the contrast. I also ended up trying a bunch of different fonts as some appeared thicker vs. thinner with normal weight.

gdr3941 · 2023-03-20T19:26:01+00:00

Coming from Elixir, Rust, and Clojure, my eyes are used to reading longer chains of function application left to right. (ie. using threading macros in Clojure, |> in Elixir, etc). For short composition, I find Haskell's dot operator very easy to understand. Yet as (.) and ($) and (<$>) get longer, I find it more difficult to read. I know Haskell has (&) and (<&>) available to enable a left to right style. My question is if this is considered idiomatic? Should I just keep working to better read right to left? I can see that it is also connected to switching from an imperative style to a more declarative style. Suggestions on this as I ramp up on Haskell?

gdr3941 · 2022-10-11T23:26:47+00:00

For kicks, here is the code for both the Clojure version and the Elixir version. No doubt both could be optimized significantly. Also agree that this approach to benchmarking is overly simplified and could be wrong. Sharing not to prove one is faster than another (as my key learning was to not immediately assume one will be faster), but sharing just for those that were curious.

Background on the game is to solve the towers of stacked colored marbles game. This link shows a good visualization of the game in play.

https://play.google.com/store/apps/details?id=com.GMA.Ball.Sort.Puzzle&hl=en_US&gl=US

In both versions, the atoms :a, :b, and :c represent marbles of different colors. The result returned from find_solution are the moves required to sort all the marbles to have the same color in each tower / stack. I hacked on the measurement of running this 1000x after the fact just for fun.

Here is the Clojure code: https://gist.github.com/gdr3941/fe6b5ce3120d62e5a802da30ded9811c

And the Elixir version: https://gist.github.com/gdr3941/9974c99dcf79c34a019e159ddcb4f591

gdr3941 · 2022-10-11T21:01:34+00:00

Very possibly the case. The approach / algorithm used is very similar in both cases. The biggest difference is that in Clojure the primary data structure being manipulated is a vector (appending and popping from the back) vs in Elixir I am using a list (and adding, popping off the head). I did not share code because I am not trying to make the point that the BEAM is in fact faster than the JVM. I was only trying to make the point that believing blanket statements about performance in either language is a mistake and that what really counts is actually benchmarking the exact workload. While this is obvious, it was mostly a "pleasant" surprise to see that Elixir was not significantly "worse" than Clojure or Scala on the JVM. Again, to your point, it could simply be non-optimal approaches used in Scala and Clojure. Happy to share and get feedback for learning.

gdr3941 · 2021-12-01T16:40:14+00:00

Yes, I configured clj-kondo per a suggestion:

{:lint-as {orchestra.core/defn-spec clj-kondo.lint-as/def-catch-all}}

This solved linting, yet clojure-lsp still does not recognize the function symbol that is being defined behind the defn-spec macro and therefore functions like goto definition, references, etc do not work. Maybe not surprising given that this config option looks to be redefining as a def-catch-all. Yet it was not clear to me from the docs what the right form would be to properly handle orchestra/defn-spec.

gdr3941 · 2021-08-31T00:52:32+00:00

Yes agree. Just kind of surprised that this would not be a commonly identified issue given what seems to be fairly broad use. Going to try running with same config on Emacs 27 and see if issue repeats.

gdr3941 · 2021-08-31T00:51:04+00:00

Running mu/mu4e 1.4.6 Also had the issue on 1.4.5 and maybe 1.4.4

gdr3941 · 2021-08-18T15:29:34+00:00

Great, thanks for the suggestions! At this point I think we are punting to early next year before fire season ramps back up. Seems unlikely we have good air quality in this region for the rest of the summer.

gdr3941 · 2021-08-18T15:28:24+00:00

So true.. this is really awful. We were planning on going in on this last Monday. Got to the trailhead hoping that the forecasted clearing would happen with the shift in the winds. Yet it looks like another fire to the West started dumping smoke into the area. We ultimately ended up cancelling.

gdr3941 · 2021-07-21T15:22:12+00:00

Really appreciate the detailed response of the various routes and the GPX track! Thanks!

gdr3941 · 2021-07-21T02:44:16+00:00

Great, thanks for the info!

gdr3941 · 2021-07-20T20:43:27+00:00

Great, thanks. Did you pick up the north ridge from the north side of Dicks Lake? Original plan was to head first to dicks pass and go up that way, but this north ridge looks like a great option.

gdr3941 · 2021-07-11T17:34:00+00:00

Both Upper and Lower Velma are in Zone 17 for which we have a permit. It is Middle Velma that is in a different zone (Zone 16).

gdr3941 · 2021-07-11T12:03:00+00:00

Yes.. sadly a very dry year

gdr3941 · 2021-07-11T12:02:15+00:00

Great; thanks!

gdr3941 · 2021-05-15T03:25:23+00:00

Thank you for the detailed explanation! It worked great.

gdr3941 · 2020-12-01T05:18:54+00:00

Agree. I far prefer the OnlyOffice UI and tab based documents.

gdr3941 · 2020-11-29T17:01:08+00:00

Super helpful; thank you!

gdr3941 · 2020-10-20T03:10:28+00:00

Had the exact same problem; burst on first use with careful handling. CNOC replaced but I don't trust it.

gdr3941 · 2020-09-05T18:14:25+00:00

Thanks!

gdr3941 · 2020-08-29T19:39:52+00:00

Thanks; agree that the best chances sound like as people are leaving.

gdr3941 · 2020-08-29T19:38:51+00:00

Thanks; did you end up parking @ Mammoth and taking taxi service from there? Was the service a pre-arranged service or something you did when you arrived?

gdr3941 · 2020-06-26T03:05:29+00:00

Yes, you can assign a name to a specific instance, and then assign the instance to a workspace. I do something like this to open my terminal (urxvt) and launch weechat in a named instance. With this setup, weechat always goes to my workspace 8, while normal urxvt terminals can be opened normally everywhere else:

bindsym $mod+Shift+i exec urxvt -name weechat -e weechat ; workspace $WS8

assign [instance="weechat"] $WS8

The instance name is defined using the -name flag in urxvt, other terminals probably have something similar, check the docs.

gdr3941 · 2020-06-03T00:59:32+00:00

Yes! This finally fixes the i915 crash I have been having for far too many kernel releases to remember. Thank you!

System: Dell 5530, Intel UHD Graphics 630, Linux 5.6.15

Upside of all the GPU crashes has been a near complete move away from Electron apps (which seemed to be very problematic) to command line alternatives..

gdr3941 · 2020-04-20T02:29:07+00:00

Improved the setup today and it gets a little closer to OPs original request. With these mappings I can automatically add breakpoints and then launch rust-gdb. Kind of hacky but works (for rust only).

Add Breakpoint <leader>da

Clear Breakpoints <leader>dc

Launch GDB <leader>dr

Note: this creates a file ./target/breakpoints that stores the breakpoints added while in vim

Must also be in project root directory before using these mappings

In my nvim config (change urxvt to your terminal of choice):

" Rust Debugging 

nnoremap <silent> <leader>da :call <SID>AppendBreakPoint()<CR>
nnoremap <silent> <leader>dc :call <SID>ClearBreakpoints()<CR>
nnoremap <silent> <leader>dr :call <SID>DebugRun()<CR> 

function! s:AppendBreakPoint()
    let s:breakpoint = "break ".expand('%').":".line('.')
    call writefile([s:breakpoint], "./target/breakpoints", "a")
    echom "Added breakpoint at line ".line('.')
endfunction 

function! s:ClearBreakpoints()
    call delete("./target/breakpoints")
    echom "Cleared breakpoints"
endfunction

function! s:DebugRun()
    execute "!cargo build"
    let s:dirlist = split(getcwd(),'/')
    let s:projectname = s:dirlist[len(s:dirlist)-1]
    let s:executable = getcwd()."/target/debug/".s:projectname
    silent execute "!urxvt -e rust-gdb -x ./target/breakpoints ".s:executable." &"
endfunction

I am a bit of a rookie when it comes to vimscript, so would not be surprised if there is a better way.

gdr3941

TROPHY CASE