David Heinemeier Hansson
03192de90e
Use a header that won't fold on a small screen
2025-07-22 16:38:33 -04:00
David Heinemeier Hansson
5e4c309b2c
Do dropbox first so we have the browser if we need it
2025-07-22 13:58:35 -04:00
David Heinemeier Hansson
a691a50559
Scaling workaround
2025-07-22 13:48:00 -04:00
David Heinemeier Hansson
778a69897b
Fix path
2025-07-22 13:37:04 -04:00
David Heinemeier Hansson
ff77d4731f
Allow it to start before existing
2025-07-22 13:23:59 -04:00
David Heinemeier Hansson
ec4efb304c
Didn't actually like that
2025-07-22 13:20:57 -04:00
David Heinemeier Hansson
1d4991426e
More shushing
2025-07-22 13:16:37 -04:00
David Heinemeier Hansson
c31250d7c0
Also can't use logo here or we're squishing
2025-07-22 13:12:35 -04:00
David Heinemeier Hansson
f36402b2c9
Clear before launching
2025-07-22 13:11:10 -04:00
David Heinemeier Hansson
ecf65b0499
Still need to keep it quiet
2025-07-22 13:10:47 -04:00
David Heinemeier Hansson
65ba4cc576
Might squish the logo when we open Docker or Manual
2025-07-22 13:09:01 -04:00
David Heinemeier Hansson
56999c0ae5
Use the Omarchy Manual webapp for launching
2025-07-22 13:06:35 -04:00
David Heinemeier Hansson
28bec8c7d2
Launch the Docker app if we installed Docker DBs
2025-07-22 13:03:14 -04:00
David Heinemeier Hansson
484b98ae43
No confirm please
2025-07-22 13:02:01 -04:00
David Heinemeier Hansson
14d9cd452c
Explain the gum picker
2025-07-22 13:01:19 -04:00
David Heinemeier Hansson
1c69965819
Restart walker when we refresh the config
2025-07-22 11:21:50 -04:00
David Heinemeier Hansson
ea903c7d65
Cleanup the screenrecording script
2025-07-22 08:58:20 -05:00
Andreas Nigg and GitHub
6d8a1e3bcf
wf-recorder instead of wl-screenrec (NVIDIA support for screen recording) ( #278 )
...
* use wf-recorder instead of wl-screenrec
wl-screenrec does not support NVIDIA drivers as of now
* install wf-recorder and migration for it
* use wl-screenrec for non-nvidia and wf-recorder otherwise
* useless comment
* only use one of the screen recording features
2025-07-22 08:47:25 -05:00
David Heinemeier Hansson
cd0565a57f
Explain where to find Dropbox icon
2025-07-21 20:38:54 -04:00
David Heinemeier Hansson
e464f19bff
Not starting right
...
Emacs people can figure themselves out
2025-07-21 20:34:09 -04:00
David Heinemeier Hansson
2567baf00e
Clear so not smushed
2025-07-21 20:31:05 -04:00
David Heinemeier Hansson
84065dd767
Cleanup terminal after each step
2025-07-21 20:29:43 -04:00
David Heinemeier Hansson
377522f804
Try a simpler setup flow
2025-07-21 20:12:58 -04:00
David Heinemeier Hansson
a7b423a2c4
No redirect since stderr has the code
2025-07-21 20:11:41 -04:00
David Heinemeier Hansson
853d46854f
Even if you kill it, you're done
2025-07-21 20:11:32 -04:00
David Heinemeier Hansson
785d575ecc
Fix installation references
2025-07-21 19:58:54 -04:00
David Heinemeier Hansson
f346c78826
Quiet stderr
2025-07-21 19:55:40 -04:00
David Heinemeier Hansson
47584de6db
Let it tile so browsers open neatly next to it
2025-07-21 19:05:32 -04:00
David Heinemeier Hansson
ac3aadd93a
Correct path here too
2025-07-21 18:50:48 -04:00
David Heinemeier Hansson
cdc9f8606e
Go to the Omarchy directory first
2025-07-21 18:45:31 -04:00
David Heinemeier Hansson
83a8f42bd7
Open the manual as the last step
2025-07-21 18:27:15 -04:00
David Heinemeier Hansson
6a3ce098e9
Use a common namespace for cmds
2025-07-21 18:26:09 -04:00
David Heinemeier Hansson
d1ba090bec
Its obvious
2025-07-21 18:13:53 -04:00
David Heinemeier Hansson
04ec2ba84d
Reuse the Omarchy title so we get the same float
2025-07-21 18:13:37 -04:00
David Heinemeier Hansson
fa5b13a284
Finalize the first-run flow
2025-07-21 18:05:48 -04:00
David Heinemeier Hansson
22ff741c7f
Hurray
2025-07-21 17:57:29 -04:00
David Heinemeier Hansson
602009ebf3
Add a first-run flow
2025-07-21 17:46:37 -04:00
David Heinemeier Hansson
0c6719becc
No longer using current/backgrounds
2025-07-21 17:12:16 -04:00
David Heinemeier Hansson
e8c23532b3
Reuse ansi art and clear install when we ask for input
2025-07-21 16:22:28 -04:00
David Heinemeier Hansson
a7fb87f08b
Need to put remove somewhere else -- not common enough to gum this up
2025-07-21 16:10:26 -04:00
David Heinemeier Hansson
e898ae327f
Use dropbox-cli so it doesn't quit when the terminal does
2025-07-21 16:09:08 -04:00
David Heinemeier Hansson
b21a236bf3
Fixup the Dropbox setup flow
2025-07-21 16:05:29 -04:00
David Heinemeier Hansson
f60e66cfdf
Move Dropbox to a setup script
2025-07-20 21:51:46 -05:00
David Heinemeier Hansson
e7da208505
Fix using backgrounds from inside the themes
2025-07-20 21:30:06 -05:00
David Heinemeier Hansson
3415fef297
Go back to just always updating system packages
...
Otherwise we can't depend on having the same minimum versions
2025-07-20 21:24:10 -05:00
David Heinemeier Hansson
9c01775287
Better to use the refresh commands so you don't forget to write the migration
2025-07-20 21:16:04 -05:00
David Heinemeier Hansson
3634235eee
Move from permission setup to .bak process
...
Means less interaction for folks just riding on the default train
without overwriting the work of people who've made changes.
2025-07-20 21:07:59 -05:00
David Heinemeier Hansson
35fb85ea5a
Revert "Temporary fix for waybar stacking on waking from sleep"
...
This reverts commit b967223d3c
2025-07-20 20:22:52 -05:00
David Heinemeier Hansson
b967223d3c
Temporary fix for waybar stacking on waking from sleep
...
Sledge hammer fix by restarting the waybar, but it'll do the job until
we find a better fix for #196
2025-07-20 20:14:57 -05:00
Richard Macklin and GitHub
f81983ec50
Fix detection of "new migrations" in omarchy-update ( #219 )
...
Previously, `omarchy-update` used the timestamp of the most recent git
commit to determine which migrations are "new" and should be executed.
Unfortunately, that strategy can (and did) fail in certain scenarios. If
a migration was generated at time T1 but not merged until time T3, and
meanwhile omarchy's `master` branch was updated to a new release with
commit timestamp T2 (where T1 < T2 < T3), then anyone who runs
`omarchy-update` between T2 and T3 would end up with `last_updated_at`
equal to T2; thus, on their next `omarchy-update` it would fail to
detect the migration with timestamp T1 as a "new" migration that should
be executed.
This commit changes the strategy for detecting "new" migrations to avoid
that problem. Rather than recording the most recent commit's timestamp,
we record its SHA. Then, after pulling the new changes, we can leverage
`git diff --name-only --diff-filter=A $SHA.. migrations/*.sh`
to return precisely the list of migration files that were introduced by
our `git pull`. It doesn't matter if any of those migrations have a
timestamp that was earlier than the timestamp of the commit we started
on - we will always execute *every* migration that didn't exist before
our `git pull`!
2025-07-20 17:55:22 -05:00
