Bobinas P4G
  • Login
  • Public

    • Public
    • Groups
    • Popular
    • People

Conversation

Notices

  1. Bernie (codewiz@mstdn.io)'s status on Saturday, 20-Nov-2021 18:53:00 UTC Bernie Bernie

    I tried #Wezterm's ssh client with multiplexing, and it's awesome.

    Now you can have local terminal splits and tabs for the same remote session, without the messy, high-latency interposition of tmux or screen.

    Plus, it's written in #Rust!

    https://wezfurlong.org/wezterm/multiplexing.html

    In conversation Saturday, 20-Nov-2021 18:53:00 UTC from mstdn.io permalink
    • Bernie (codewiz@mstdn.io)'s status on Saturday, 20-Nov-2021 18:59:50 UTC Bernie Bernie
      in reply to

      The main downside with #Wezterm is that there's no configuration UI, and the config file is a Lua script.

      I had to _actually_ rtfm just to change the font and the background color! 😫

      In conversation Saturday, 20-Nov-2021 18:59:50 UTC permalink
    • Srevin Saju (srevinsaju@mstdn.io)'s status on Saturday, 20-Nov-2021 19:03:32 UTC Srevin Saju Srevin Saju
      in reply to

      @codewiz I moved over to Wezterm, and another thing I like about it is that, by just having a single configuration file, I can have the same terminal experience across all desktop environments and all of my devices! My terminal would look and perform just exactly the same :D

      In conversation Saturday, 20-Nov-2021 19:03:32 UTC permalink
    • Bernie (codewiz@mstdn.io)'s status on Saturday, 20-Nov-2021 19:27:48 UTC Bernie Bernie
      in reply to
      • Srevin Saju

      @srevinsaju Yes!!!

      But the property we need for sharing configuration across machines isn't exactly a single config file: config files must be free from absolute paths and other properties that change from one machine to another.

      Wezterm's Lua config makes it easy to split machine-local configuration to a another file, such as ~/.local/share/wezterm/local.lua

      But really, all programs should be doing this, without requiring a programming language for configuration.

      In conversation Saturday, 20-Nov-2021 19:27:48 UTC permalink
    • Bernie (codewiz@mstdn.io)'s status on Sunday, 21-Nov-2021 00:48:47 UTC Bernie Bernie
      in reply to
      • Srevin Saju
      • William W

      @srevinsaju @silico_biomancer Sure, but .vimrc was already a full-blown programming language... and quite an awful one! Of course Lua looks neater...

      The main problem with config files being programs is that they the UI can't easily edit them.

      I think VSCode's settings.json is a reasonable compromise that's flexible enough for most advanced users while being machine-editable.

      In conversation Sunday, 21-Nov-2021 00:48:47 UTC permalink
    • Srevin Saju (srevinsaju@mstdn.io)'s status on Sunday, 21-Nov-2021 00:48:48 UTC Srevin Saju Srevin Saju
      in reply to
      • William W

      @silico_biomancer @codewiz Yes! I moved my neovim configuration to lua recently, and I am still learning them, but it looks neater now!

      In conversation Sunday, 21-Nov-2021 00:48:48 UTC permalink
    • William W (silico_biomancer@cloudisland.nz)'s status on Sunday, 21-Nov-2021 00:48:51 UTC William W William W
      in reply to
      • Srevin Saju

      @codewiz @srevinsaju lua files seem like the ideal config style to me. You get so much flexibility for free. The only thing you need to overcome most downsides is to be able to create a default/reference config with all options pre-filled and commented

      In conversation Sunday, 21-Nov-2021 00:48:51 UTC permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • Privacy
  • Source
  • Version
  • Contact

Bobinas P4G is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Bobinas P4G content and data are available under the Creative Commons Attribution 3.0 license.