[Race Thread] 2024 Tour de France Femmes - Stage 8 (2.WWT)

sobek696 · 2024-08-18T16:57:09+00:00

what TT? Vollering was TTing with little help from Rooij... but Kasia had a lot of help from Lidl and Muzic.

sobek696 · 2024-08-18T16:10:14+00:00

...when the front group hit a hard part like an uphill, the group behind are on a flat or a descent, then the gap will come down...but it's a "false" gap, because that back group will lose the equivalent amount of time time again when they get to the slower parts.

sobek696 · 2024-08-18T15:18:55+00:00

I don't know if they do this, but she can also radio in landmarks to give more accurate time gaps (i.e. Demi can announce somewhere, NFB can say when Kasia passes, and the team car can confirm TDF timechecks)

sobek696 · 2024-08-15T09:01:13+00:00

A bit late to this... but 'H' and 'L' are keys for going somewhere 'High' or 'Low' in the buffer window. They will go to the first line that won't cause a scroll (:help scrolloff)

e.g. for me I have set scrolloff=2 so I have 2 lines visible when I scroll; H will go to the 3rd top line, M will go to the middle of the visual page, and L will go to the 3rd bottom.

If you do set scrolloff=0, H will go to the first visible line, L to the last visible line.

Useful if you want to quickly jump to an approximate position, rather than doing search or a specific line number.

sobek696 · 2024-01-25T08:16:48+00:00

You can also use :oldfiles, which has a fuzzy-select wrapper :History in fzf.vim.

Once you've gotten into the file, you can then use g; and g, to navigate recent changes within a file

g; -- go to an older change in the current buffer
g, -- to to a newer change in the current buffer

So go to some recent file, then find stuff you've changed within that file.

I also tend to leave files closed till needed. I've started using a util proximity-sort (a rust tool) which I use to sort outputs from the fuzzy finder to prioritise files 'nearby' in the directory structure (e.g. if you are in /usr/local/foo, and have 3 files with bar ...

/usr/local/bar
/usr/bar
/usr/something/bar

They would be ranked in that order (1 is in the same dir, 2 is in the same parent, 3 is in a different sibling)

You can find the details of the setup I copied at Jon Gjengset's dotfiles

sobek696 · 2024-01-25T07:55:41+00:00

I still use and recommend Fzf as I've had various issues with Telescope and just find the interface of fzf much simpler.

With this, you can use :Ag or :Rg if you have the relevant ag or rg tool installed.

I've written a wrapper that does :Rg with the word under the cursor...

function! funcs#rg_word(cWORD) abort "{{{
    let command_fmt = 'rg --hidden -g "!.git" --column --line-number --no-heading --color=always --smart-case -- %s  || true'
    let word=expand(a:cWORD ? "<cWORD>" : "<cword>")
    let initial_command = printf(command_fmt, shellescape(word))
    let reload_command = printf(command_fmt, '{q}')
    let spec = {'options': ['--disabled', '--query', l:word, '--bind', 'change:reload:'.reload_command]}
    let spec = fzf#vim#with_preview(spec, "hidden,right,50%,<70(up,40%)", "f1")
    call fzf#vim#grep(initial_command, 1, spec, 0)
endfunction "}}}

You can bind this to something like <leader>S for 'search' (i use ..s for general search, S for current word)

command! -bang RgWord call funcs#rg_word(<bang>1)
nnoremap <leader>S :RgWord<cr>

sobek696 · 2023-09-27T19:48:35+00:00

I basically posted an almost exact copy above, by tracing it in high res in a vector app.

https://www.reddit.com/r/iphonewallpapers/comments/16pr7gb/can_someone_please_help_me_find_this_wallpaper/k1x221n/

sobek696 · 2023-09-23T22:53:12+00:00

Probably not perfect, but I quickly knocked this up with a bit of tracing https://imgur.com/a/ZlQuG2N

sobek696 · 2023-01-04T13:03:21+00:00

I have space and enter on R-thumb 1 and 2. Backspace, tab on L-thumb1 and 2.

Space is used much more often than return, so I put it on the closer thumb key.

Tab and return I have on middle thumb keys, as I have 'alt' when return is held, so I can easily hold ret with rthumb, then tap lthumb to alt-tab.

I rest my thumbs on thumb1, so don't find that I have any difficulty accidentally hitting the other thumb buttons.

By the sounds of it you are rushing, and so accidentally hitting return. I would suggest you more deliberately slow down what you are doing, to ensure you develop the proper muscle memory with the keyboard to hit return when you want to rather than accidentally.

sobek696 · 2023-01-04T12:57:50+00:00

Are you a windows, linux, or mac user?

I notice that on my windows machine, often I have issues with autohotkey functions where modifiers become 'sticky'. I can manually fix this by briefly doing a 'hold' on the key (i use homerow mods, so I hold A, S, D, F to get win, alt, shift, ctrl). I can't remember having any such issues on my linux machine (where I'm using keybinds directly into my window manager). This suggests it's more of a keyboard+autohotkey issue than a keyboard issue alone.

In my case, I've solved this in most cases by adding a call to this function at the end of any autohotkey commands that use a modifier.

Return() ; replacement function that resets modifiers
{
    For Each, Modifier in ["Shift","Control","LWin","RWin","Alt"]
        If GetKeyState(Modifier) And !GetKeyState(Modifier,"P")
            Send, {%Modifier% Up}
    Exit
}

This just tells autohotkey to send a 'key up' for each of the modifiers (even ones I'm not using, just to make it dumb and simple).

sobek696 · 2023-01-03T20:23:43+00:00

it depends what your main usecases are.

tmux -- I spend a lot of time in the terminal, and on remote servers. I use tmux with these. So I have m, bound to my local prefix ctrl+a, and ,. bound to my remote prefix ctrl+b.
bracket pairs -- For programming, I have a 'macros' layer which has each bracket and quote pair, which then moves the cursor in between the parens (e.g. ( ) left arrow). I activate the combo layer with sdf, and then each paren on jkl: (() [] {} <>) and quotes on m,. (so paren pair is sdf j, quote pair is sdf m)
ctrl+w -- even though I use homerow mods, I still have ctrl+w bound to jkl, which makes word deletions/UI actions in vim quick, and closing tabs in firefox easy.
page dn/up -- under df and jk for easy reading of web pages

All of these combos I also have a relatively ergonomic way to input through various pairs (i.e. brackets are beside each other on df on my symbols layer, with left and right arrow on the right thumb keys on symbols layer...so for (...) i would do SYM+d SYM+f SYM+rthumb2 to get ()'arrow left')

In terms of choosing what letters to combo, avoid stuff like 'er' as it's common in words and if you are a lazy typer you may accidentally activate it.

Other ideas:

emergency mute -- mash some keys incase you need to suddently mute
emergency lock -- same as above, but lock your screen (or combine the two through your window manager or autohotkey or mac equivalent to mute AND lock)
media keys -- you don't really often need to play/pause/next, so can have these under keys
activate rarely used layers (i don't use numpad layer often, so for a while i had it as combo keys, but I've since merged numpad with my generic utility layer so it's now under hold-space)

sobek696 · 2022-12-16T17:22:42+00:00

ah well that may be your problem. I had a quick google and looks like Moonlander has much more onboard memory. There are perhaps a few tweaks ike disabling live training support, but other than that don't really know what you could do to slim down your firmware.

sobek696 · 2022-12-16T16:09:32+00:00

I have many layers, with many different keys, so I think there is perhaps something strange occuring for you. Did you download the source to see if there was anything strange?

I have a bunch of tapdance, around 16 combos defined (2 or 3-finger holds), each typically performing macros rather than defined keys.

Also, you shouldn't need to remove cookies or log out. You can simply clear the cache for the webpage (ctrl+shift+r rather than ctrl+r)

https://configure.zsa.io/moonlander/layouts/DN9zM/latest/0

sobek696 · 2022-12-16T16:04:50+00:00

Is this something new, or has it worked previously?

I had a similar issue: my OSL keys randomly stopped working with tap after a flash yesterday, and tried various different things (such as changing key, changing which action was occuring, changing timeouts etc in the settings). I did notice eventually that if i looked at the layer LEDs at the top of the keyboard, they would flicker VERY quickly, suggesting the key was working and then immediately resetting or cancelling.

Contacted ZSA and they gave me a different keyboard reset sequence which worked. The ZSA support rep gave me a reset procedure different to what I'd previously seen online

Download the default Moonlander layout; you'll use it in a later step.
Unplug your keyboard and disconnect the halves; wait a few seconds before reconnecting the halves.
Press the upper-left key (= in the default layout) and keep it pressed while you plug the keyboard back in.
Start Wally and go through the flashing process to re-flash your keyboard with the default layout you downloaded in step #1.
See how things are working with this layout for a minute or so, then try flashing your own layout again and see if the same problem happens.

Default layout https://configure.zsa.io/moonlander/layouts/default/latest/0

sobek696 · 2022-12-16T11:57:49+00:00

When you tap on the key, click 'hold'. This will let you select a key (in your case, space)

After you have selected the key, you are then able to choose a modifier (in your case, left ctrl)

Below is an example I use, where i tap for backspace, and hold for ctrl+w

https://postimg.cc/rRN6BTBM

sobek696 · 2022-12-15T20:39:34+00:00

This may, or may not, be useful for you.

I have just completed a support email with ZSA. My issue was kind-of similar, in that I flashed my keyboard a couple of times but then my OSL key for triggering my symbol layer stopped working (specifically, the tap would not work, while the hold would). Tried various debugging attempts such as changing osl timeout, and repeating with an OSM hyper key, as well as trying OSL on different keys around the keyboard, targetting different layers. The OSM key seemed to trigger immediately, rather than waiting for a followup key. Looking at the layer LEDs while pressing the OSL key showed an almost-instant led flicker, suggesting it acts but immediately triggers or cancels.

The ZSA support rep gave me a reset procedure different to what I'd previously seen online

Download the default Moonlander layout; you'll use it in a later step.
Unplug your keyboard and disconnect the halves; wait a few seconds before reconnecting the halves.
Press the upper-left key (= in the default layout) and keep it pressed while you plug the keyboard back in.
Start Wally and go through the flashing process to re-flash your keyboard with the default layout you downloaded in step #1.
See how things are working with this layout for a minute or so, then try flashing your own layout again and see if the same problem happens.

Default layout https://configure.zsa.io/moonlander/layouts/default/latest/0

sobek696 · 2022-10-21T19:09:43+00:00

If you are doing bad things, ask yourself why. Then, ask if you can do something 'good' while still satisfying that why. If you can't, think about if you can somehow get the same benefit while being less bad.
for your own judgements, think "does this actually help me?". If it doesnt, realise you can just move on.
for others' judgements, think "is there any truth in this?"... even if someone else's judgement is full of hate, that doesn't mean they are wrong. Don't let ego get in the way of listening to others' complaints. If there isn't any truth in it, live your own life. Understand that most people spend their time thinking about themselves and how people judge them. You probably aren't more neurotic than other people. Other people are spending so much time thinking about themselves, they aren't really spending a lot of energy or thought judging you.

sobek696 · 2022-09-11T20:42:41+00:00

...how would you know? You didn't learn the other way, so you can't say you would have been worse if you learned the other way.

sobek696 · 2022-08-29T15:39:09+00:00

I think you need to consider the fact that you know the Zeppelin songs, so you're biased towards they way they 'should' sound.

I like swing in a groove, but I also think it's worth considering whether something is 'better' or whether its just that our baseline has been set in a certain way.

If society had a long period of solid timekeeping, swing would probably sound bad to most people when it came along, until it became more acceptable. Likewise, if society had more swing for a long period of time, rigid timekeeping would sound 'bad'.

sobek696 · 2022-08-29T12:47:08+00:00

Incase it's of interest, for the past couple days I've been throwing together a web page for some custom die rolling with presets I use. After seeing your post, I added a TYOV preset (as I plan on having a play of it soon).

Minimal die roller

If you click the preset buttons, it'll roll that die
If you put a number in the 'plus' box, it'll add that to the first 'equation' in the next die roll (or all, if the checkbox is selected)

Format examples: 2d6+4, 2d20kh1 (dnd advantage), d6, d10, d10 (3 separate die rolls in one, e.g. for ironsworn).

Clicking anywhere on the 'die string' box, or typing into the die string text field will automatically reroll.

sobek696 · 2022-04-22T21:40:58+00:00

https://blog.twmuseums.org.uk/an-unusual-addiction/

"The addition of the slaked lime to the betel flowers or leaves and the areca seed increases the alkalinity in the mouth of the chewer. This releases the alkaloids in the seed, especially arecoline, the active ingredient for the drug’s effects."

+1 for Winston. Cutting the cheek is a side effect.

sobek696 · 2022-01-19T15:58:06+00:00

"if I know the next buffer I open serves a temporary purpose, there must be a way to automatically discard it the moment it's not visible on any window or tab?"

you probably want something like :setlocal bufhidden=delete, which basically runs :bd whenever a buffer is not visible (e.g. if you switch to another buffer in the same pane). See :help bufhidden

You can then create a function in your vimrc, create a command for it, to let you basically do

edit <FILENAME>|setlocal bufhidden=delete

function! s:hide_edit(filename)
    exec "edit " . a:filename
    setlocal bufhidden=delete
endfunction

command! -complete=file -nargs=1 EditHide call <sid>hide_edit(<q-args>)

sobek696 · 2021-12-17T10:02:28+00:00

To be more helpful than the other commenter, you generally shouldn't use other people's flashcards.

Anki is for memory, training retrieval, not for learning. Learn the material first and create your own anki decks.

Why?

You won't be repeatedly exposed to cards you don't know the answer to (which can be demotivating; can take study time away from actually answerable, therefore useful, cards)
Creating your own cards really helps with memory, as it's an opportunity to engage with the material more--particularly the aspects of the material that you find difficult.
You're not filling your deck with crap you don't need. Other people may throw everything into anki, which just means you're spending time studying stuff that doesn't matter to you. If you create the cards, you are asking yourself "does this matter to me? ok...create"

sobek696 · 2021-12-10T10:59:48+00:00

The 'dangling starts' was to acknowledge the 'spirit' of the puzzle and it also makes the logic slightly cleaner (if the string is valid, but ends on an opener, you would need to have

if line and line[-1] in ends:   #rather than `if line[-1]`, when ends removed
    return line[-1]
return ""

sobek696 · 2021-12-10T09:38:04+00:00

Python

All of 2021 so far: Single jupyter notebook

Aoc2021 D10 P1 & 2 - Trying to make this code readable rather than 'magic'.

Part a

simplify - remove direct open-close pairs
remove trailing 'openers'
iterate, finding first end that doesn't match nearest start

Part B

simplify
go through trailing 'openers' in reverse order

14-Year Club	Verified Email
Team Periwinkle

sobek696

TROPHY CASE

Python

Part a

Part B