tmux-plugins/tmux-resurrect

node-dev / restore functionality

Open

#44 opened on Sep 18, 2014

View on GitHub
 (26 comments) (0 reactions) (0 assignees)Shell (12,753 stars) (509 forks)batch import
bughelp wantedopinion wanted

Description

Hey nice useful project here.

I noticed set -g @resurrect-processes '"~node-dev"' doesn't work, but i think set -g @resurrect-processes '"~node"' did restore, but restored only a blank node session, not my original node-dev index.js command.

I think node-dev actually calls node and the process runs as node.

What if tmux-restore detected whether a window had a process running, and you based restoring on the command that caused that program to run?

If I add node to my processes, i get a terminal that runs as if I had merely called node by itself, and it appears not to care what initially spawned the process.

This could be possible, right, by sniffing the history? I see the list of processes as a whitelist, interested by the currently running processes during a save. If they match, then run the same command again. Right?

Contributor guide

Tech stack
shellnodejs
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
tmux basicsshell scriptingtmux resurrect internalsnode dev usage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Review the save and restore scripts in the tmux resurrect repository, particularly how processes are matched and restored. Look at the comments in this issue for suggested approaches, especially around using process history or shell history to capture the original command. The goal is to modify the restoration logic to detect the original command that spawned the node process, possibly by reading shell history files or using process accounting. Then implement a mechanism to store and restore the full command line for node dev processes.