I was rambling a bit when I wrote this (had just got home), I'll add your
suggestion to the todo list, but if you want to send me the changes it'd be
great :-).


On Sat, Jan 23, 2010 at 02:42:42AM +0000, Nicholas Marriott wrote:
> On Fri, Jan 22, 2010 at 04:21:06PM -0500, Sudish Joseph wrote:
> > Nicholas Marriott <nicholas.marri...@gmail.com> writes:
> > > On Thu, Jan 21, 2010 at 01:33:56AM -0800, Robin Lee Powell wrote:
> > >>   Why does "tmux new-session vim \; split-window \; attach" not
> > >>   work? Why does it need the -d, I mean?  Seems like attaching a
> > >>   session shouldn't stop the split-window command from being
> > >>   proccessed.
> > >
> > > new-session without -d implies attach and that stops further command
> > > processing, although I can't remember why and it probably shouldn't.
> > 
> > That clarified a lot for me and would make a great one-line addition to
> > the man page para for new-session.
> 
> Thanks for your suggestion,
> 
> I'd appreciate it if you could send me a man page diff - mdoc looks bad but it
> isn't really that hard.
> 
> Or failing that send me a one line diff against TODO so it isn't forgotten.
> 
> I am super super busy right now, so I can't pick up all the "it'd be great"
> suggestions.
> 
> tmux is still a priority, but I also have a ton of other stuff on my todo 
> list:
> work, OpenBSD and $otherstuff.
> 
> I prioritise stuff with diffs, or good bug reports, so if you send a diff or
> logs or a backtrace it'll be bumped to near the top of the list, although I 
> try
> to at least send a "hey, i got this" reply to every mail or bug report I
> get. If your mail has a diff it will /not/ be forgotten, even if it takes a
> while.
> 
> tcunha can maybe review or investigate some stuff but I don't know if he is up
> for that?
> 
> Suggestions for process changes are also welcome but please bear in mind that
> I'm not going to do anything right now that means more work for me, even if it
> makes things easier for others. And anyone who mentions the word "wiki" 
> without
> a URL and an offer to manage it future will be shot.
> 
> Plus I'm hiking this weekend :-).
> 
> > I just switched to tmux and until I saw this thread was using the
> > following to launch a new tmux session with a specific window/pane
> > config (from a script):
> > 
> > tmux new-session "tmux new-window \\; source $conf_file"
> > 
> > (I want ~/.tmux.conf to be read in first, $conf_file is a more specific
> > config and so tmux -f doesn't suffice here.)
> 
> Somone suggested per-session config files before but I'd like to do it as part
> of adding hooks - well, I did it, but so far I've been too afraid to
> finish/commit it because I'm not confident there aren't strange side-effects.
> 
> > 
> > What was unintuitive was why, for e.g., "tmux new \; source ..."
> > wouldn't run the "source" command.  Makes sense in light of the above.
> 
> tcunha wrote a section for the FAQ about escaping things in #(). Maybe that
> should be expanded?
> 
> > Also, 'tmux new "tmux source ..."' didn't work either, iirc. The
> > explicit neww was needed in the 2nd tmux invocation above -- I assumed
> > that 'tmux new' doesn't create a new window if passed a shell command(?).
> 
> Running tmux from inside tmux is always a bit strange but if you can send me
> the exact command line you are using, tell me your platform and a description
> of what happens, I'll try to have a look.
> 
> > This is all much cleaner with 'new -d' -- no subshells or subsequent
> > tmux invocations:
> > 
> > tmux new-session -d \; source $conf_file \; attach
> >
> > Letting 'tmux new' continue processing is intuitive and very readable,
> > imo:
> > 
> > tmux new \; source $conf_file
> 
> Yeah it would be nice but someone has to sit down and add some code to make it
> happen. I don't even know offhand why it doesn't work, I'd have to give it a
> go.
> 
> > Tmux's separation of concepts is very clean and I'm liking it very much
> > so far, thanks for the great software!
> 
> Thanks :-).
> 

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users

Reply via email to