It might be useful to look up the current tmux session, and allow users to run smug stop without a session name within a smug managed session, by using tmux display-message -p '#S'1 and looking to see if it matches an expected session name.

I'm trying to get this layout, but I don't succeed. Can you help me with an example ?

|-----------------------|-----------------------|
|                       |                       |
|                       |         echo 2        |
|                       |                       |
|      echo 1           |-----------------------|
|                       |                       |
|                       |         echo 3        |
|                       |                       |
|-----------------------|-----------------------|

We want to add an ability to create and edit configuration files within smug command.

smug <edit|create> <project> should open ~/.config/smug/project.yml in the $EDITOR

This is a simple task, and doesn't require any prior knowledge of the project. If you would like to contribute, reach me out, I'll be happy to assist with any questions.

Thanks for creating this! Per the title, I'm having trouble getting tmux to start/attach properly using smug. I'm running macOS 11.2, iTerm2 3.4.3, tmux 3.1c installed via Homebrew.

My config, intent is to start a session with a single window containing my Zettellkasten.

$ cat ~/.config/smug/zettel.yml
session: zettel

windows:
  - name: wiki
    commands:
      - vim +VimwikiIndex

Attempting to run it:

$ tmux ls
no server running on /private/tmp/tmux-501/default

$ smug start zettel
Starting a new session...
Cannot run "tmux kill-window -t zettel:0". Error exit status 1

$ smug start zettel:wiki
Starting a new session...

I'm returned to my shell prompt, and tmux does not open, but it was started!

$ tmux ls
zettel: 2 windows (created Mon Dec 21 17:15:45 2020)

Once I run tmux attach I see that 2 windows have been created. A blank shell which is the window I'm started in, and the wiki window.

Hope I've provided enough info to help, let me know if there is a debug/verbose mode I can try out, or anything else!

What?

• Adding smug create <project> to create a .yml file at ~/.config/smug If the file already exists, the terminal will output "File already exists"

• Adding smug edit <project> to edit an existing .yml file on the $EDITOR (or vim, if $EDITOR is not set) If the file doesn't exist, the terminal will output "[...]no such file or directory"

Testing?

Working on it.

Anything that can improve?

I think it would be great to add autocomplete on tab when using smug edit <project> so it shows any existing projects on ~/.config/smug. This could be done with the complete package.

Screenshots (Updated: 31 December, 2020)

https://user-images.githubusercontent.com/45673971/103425323-365a2180-4b77-11eb-9f28-57d92d5057fa.mov

I am excited to see another competitor to tmuxinator. I would love to drop it since its my only ruby dependency left in my dotfiles.

Wondering if there are plans to support passing in arguments to projects when invoking smug. This is the only feature of tmuxinator that I use that would make switching a little bit differerent. I have scripting around launching projects in tmux, if a tmuxinator/smug project would exist it would launch that, otherwise it launches a default project that gives me some standard windows. In tmuxinator it looks like this.

name: <%= @settings["name"].upcase().split(/[-_]/).join(' ') %>
root: <%= @settings["root"] %>

windows:
  - editor: nvim
  - console: clear

I could move this to a custom script instead of using smug/tmuxinator but it was kinda nice defining it and keeping it in tmuxinator.

Describe the bug I have a config defined with two windows. One is configured as manual: true. I open a session with smug start myconfig. This opens the first window successfully with the configured panes and commands.

Then I smug start myconfig:test2 which is the manual one. It fails to open.

Smug config

session: 'MyConfig'
windows:
  - name: test1
    commands: [ls]
    panes:
      - commands: [ls]
  - name: test2
    manual: true
    commands: [ls]
    panes:
      - commands: [ls]

Expected behavior The test2 window should open successfully with the defined layout

Output of cat ~/.config/smug/smug.log

tmux has-session -t MyConfig:
tmux neww -Pd -t MyConfig: -c  -F #{window_id} -n test2
tmux send-keys -t @3 ls Enter
tmux split-window -Pd -t @3 -c  -F #{pane_id}
tmux select-layout -t @3 tiled
tmux send-keys -t @3.%6 ls Enter
tmux select-layout -t @3 even-horizontal
tmux kill-window -t MyConfig:smug_def
exit status 1 can't find window: smug_def

tmux kill-window -t MyConfig:test2

It seems smug_def window is not being created in this scenario, which is expected to exist.

Smug version

Smug - tmux session manager. Version 0.3.1

OS you're using MacOS Monterey 12.4

This PR closes #84.

It accomplishes this with two main changes:

Env Vars

It adds three env vars to all smug-created tmux sessions.

• $SMUG_SESSION - always equal to "true". Allows users to do easier scripting and detection if it's a smug-managed session
• $SMUG_SESSION_NAME - name of the tmux session smug created
• $SMUG_SESSION_CONFIG_PATH - full filepath of the smug config file that created this session

Config parser

If the --file arg is not specified, but $SMUG_SESSION_CONFIG_PATH is set, the value of the env var is put into the --file value variable, allowing all normal commands that would work with --file manually specified to work automatically within a smug session. This lets smug be aware of it's current context if existing within a smug session, and operate on it by default unless you force it to do something else. For example, smug stop or smug edit work without any additional args.

I'd love support for short commands, like tmux does.

In cases where there's no ambiguity, it would be very handy to be able to use "n" for "new", "e" for "edit", "l" or "ls" for "list", etc.

Of course, cases like "s" would be ambiguous (start/stop), so would need to be used in it's fuller form, the same way tmux does.

I've been maintaining the ArchLinux AUR for smug and I noticed that the tag for v0.2 didn't update the version string in main.go. Obviously not a high priority thing but I figured I'd report it since I noticed it.

In some situations send-keys might fire before the shell prompt finished initilization. It happened for me when using fish shell and oh-my-fish which makes the send-keys start executing bofore my shell is ready and I endup with a written command that is not executed

This patch adds a custom sendkeys_timeout as a top level option that takes an integer in milliseconds. It will ensure a Sleep call is made before.

I want to allow users to group their configs into directories, e.g:

smug
├── my-awesome-project
│   ├── app.yml
│   └── backend.yml

Now command smug start my-awesome-project should create multiple tmux sessions, and attach to the last one created. Config option always_attach: true on the config root level may be added

[feature request] ready-command

ready-command: - do-this-then-that-later

This would allow to have the command echoed to the prompt but NOT yet executed.

Describe the bug If there are two or more smug config with name prefixed from one of them, and then the prefix of the name itself is running last (as it uses $(smug config)

To get the situation here:

• Running a smug config will give you a list, with prefixer to come later from prefixed name.
• Executing whole batch using for VAR in $(smug config) will execute everything except the last one, due to prefixing issue. On the picture it's yohane-irc vs yohane which is shadowed by yohane-irc upon doing smug start yohane until the yohane-irc window got stopped.

However:

• If I decide to smug config | sort, or at least sorting the naming order from smug config output, which happens to give different output from just smug config. Things works normally.
• Execution order changed from yohane to yohane-irc instead vice versa. No naming conflict like what happened above.

Smug config smug config does not matter

Expected behavior

• Both yohane-irc and yohane should be executed alongside in any order of execution.

Output of cat ~/.config/smug/smug.log output log does not matter.

Smug version 0.2.7

OS you're using Linux

Tmux has the -L option to specify the socket name (and -S to specify the socket path). This is very useful to group sessions in different sockets (isolated tmux servers).

It would be nice to have this option in smug.

Other tmux managers allow users to set the socket name in the yaml files which I haven't used, but could also be useful.

I have the intention of creating a PR for this, but I would have to learn at least some basic Go to do this 😅

What do you think @ivaaaan? Do you see value in this? Should I create a PR or is it easy for you to do?

Thank you!

If you implement this CLI library you loose a lot of overhead code for your commands and options. Beside this you get usage documentation and autocomplete without extra coding. If you like I can help.