Mateen Ulhaq

Any type of window (pinned, floating, or special workspace) should be fullscreenable. Rationale: - I put my dropdown terminal in the special workspace. Sometimes I want it to maximize it...

@marianozunino I ended up switching back to i3 since (i) I missed the flexibile design of i3 "scratchpads" in comparison with Hyprland special workspaces, and (ii) Wayland is missing OBS...

**Quick n' dirty:** I think that syntax highlighting both portions (even if incorrect) is less disastrous than not highlighting the code at all. Perhaps a quick and simple workaround would...

@Pyrestone My workaround. Not sure which one of these was the necessary one (probably `meta/progress` or `meta/locks`, I'm guessing), but try one of the following: ```bash touch .aim/meta/progress/$RUN_HASH touch .aim/meta/locks/$RUN_HASH...

@Pyrestone Ah, I think I also removed some of the relevant $RUN_HASH.softlock files from the .aim directory as well. I remember it was some combination of deleting and touching files...

Depending on the remote, you may be able to set `--host=0.0.0.0` (i.e. "bind all incoming connections"). --- On the remote server: ```bash aim up --host=0.0.0.0 --port=16007 ``` Then, from your...

In my case, the host machine is on a local network within our organization. This is good because I can share a link to other members on my team. But...

> * pass it through via a separate `new_run_hash: Optional[str] = None` param to mitigate the "Run creation due to typos" concern discussed in [Restrict Run.hash to auto-generated values only...

Possible use cases: - Customizing the run hash format to e.g. ` ` `deadbeef20230101235959ac` ...or anything else which may be meaningful to the user. Since the hashes are being randomly...

> ...as the script properly closes the Run. Is this a requirement? I suppose the correct program flow would then be: ```python def do_stuff(run): ... try: run = aim.Run(...) do_stuff(run)...