aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMelody Horn <melody@boringcactus.com>2020-12-05 11:34:43 -0700
committerMelody Horn <melody@boringcactus.com>2020-12-05 11:34:43 -0700
commit8add0012b9c1c61e5c4108443fcb9d16978318f1 (patch)
treee95e2677e99dd31d1cc143f9c45255c3da942dcc
parent8b13787b9e471f475a31d6ffa4c522e6de006746 (diff)
downloadboringcactus.com-8add0012b9c1c61e5c4108443fcb9d16978318f1.tar.gz
boringcactus.com-8add0012b9c1c61e5c4108443fcb9d16978318f1.zip
fix more list issues
-rw-r--r--_posts/2020-03-20-mobaxterm-desktop-session.md8
-rw-r--r--_posts/2020-08-21-survey-of-rust-gui-libraries.md10
2 files changed, 9 insertions, 9 deletions
diff --git a/_posts/2020-03-20-mobaxterm-desktop-session.md b/_posts/2020-03-20-mobaxterm-desktop-session.md
index ae12a98..f8576c7 100644
--- a/_posts/2020-03-20-mobaxterm-desktop-session.md
+++ b/_posts/2020-03-20-mobaxterm-desktop-session.md
@@ -5,10 +5,10 @@ title: "Lifehack: Running An Entire Desktop Session Remotely With MobaXterm"
Since my university has gone as remote as possible due to coronavirus, I was looking at ways to run an entire desktop session remotely over SSH, using MobaXterm because it is very cool.
Here are the two steps to doing that.
-1. Open your MobaXterm settings, go to the X11 tab, and make sure that the server display mode is set to windowed mode.
-If you run individual programs over X11 forwarding, this is worse, but for an entire desktop session it is better.
-2. Duplicate your regular command line session that already works, and under the "Advanced SSH settings" tab, set "Execute command" to `env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu`.
-(If you're not running the same setup I am, look around in `/usr/share/xsessions/`, pick something that looks reasonable, and use everything after `Exec=` on the line with that.)
+1. Open your MobaXterm settings, go to the X11 tab, and make sure that the server display mode is set to windowed mode.
+ If you run individual programs over X11 forwarding, this is worse, but for an entire desktop session it is better.
+2. Duplicate your regular command line session that already works, and under the "Advanced SSH settings" tab, set "Execute command" to `env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu`.
+ (If you're not running the same setup I am, look around in `/usr/share/xsessions/`, pick something that looks reasonable, and use everything after `Exec=` on the line with that.)
At this point, you should be set.
You'll need to hit the "log out" button to smoothly exit the connection.
diff --git a/_posts/2020-08-21-survey-of-rust-gui-libraries.md b/_posts/2020-08-21-survey-of-rust-gui-libraries.md
index e9ab8be..aaaa954 100644
--- a/_posts/2020-08-21-survey-of-rust-gui-libraries.md
+++ b/_posts/2020-08-21-survey-of-rust-gui-libraries.md
@@ -150,12 +150,12 @@ if you're curious, you can take a look at [the source for our druid example](htt
so apparently druid is actually pretty darn usable.
i only have a couple tiny issues with it:
-1. it doesn't use platform native UI widgets, so it doesn't look quite like a windows app should, and it won't look quite like a mac or linux app should either if i test it there.
-this one is a feature as far as some people are concerned, but i am not on that list.
+1. it doesn't use platform native UI widgets, so it doesn't look quite like a windows app should, and it won't look quite like a mac or linux app should either if i test it there.
+ this one is a feature as far as some people are concerned, but i am not on that list.
2. accessibility features like being able to tab between UI widgets are missing, so you'd have to roll those yourself in a real application.
-maybe they'll add that by default in future versions, maybe not, but it would be neat if it existed.
-3. high-level documentation is incomplete.
-the individual struct/function docs are really good, but at a high level you don't really have a convenient place to jump in.
+ maybe they'll add that by default in future versions, maybe not, but it would be neat if it existed.
+3. high-level documentation is incomplete.
+ the individual struct/function docs are really good, but at a high level you don't really have a convenient place to jump in.
i was about to add "no support for web" to that list, but even though the high-level docs don't mention it, the crate root docs and the examples do.
on the plus side, it just works, and i didn't have to make any changes to my code because i use [this patch to wasm-pack that lets you just use binary crates in wasm-pack](https://github.com/rustwasm/wasm-pack/pull/736) even though it hasn't been merged yet upstream.