Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#109 Periods no longer allowed in session names

closed
nobody
None
2014-04-22
2014-03-05
Xiong Chiamiov
No

In tmux 1.8 and earlier, periods were valid in session names. I found this useful, as I use sessions that map directly to directories on the filesystem, and I have projects named things like 'xiongchiamiov.github.com'.

As of tmux 1.9a, attempting to create a new session gives an error:

[$]> tmux new -s a.s
bad session name: a.s

I don't know if this was intentional, but I didn't see it (or anything seemingly related) in the changelog.

Related

Tickets: #109

Discussion

  • Thomas Adam
    Thomas Adam
    2014-03-05

    On Wed, Mar 05, 2014 at 03:19:48AM +0000, Xiong Chiamiov wrote:


    [tickets:#109] Periods no longer allowed in session names

    Status: open
    Created: Wed Mar 05, 2014 03:19 AM UTC by Xiong Chiamiov
    Last Updated: Wed Mar 05, 2014 03:19 AM UTC
    Owner: nobody

    In tmux 1.8 and earlier, periods were valid in session names. I found
    this useful, as I use sessions that map directly to directories on the
    filesystem, and I have projects named things like
    'xiongchiamiov.github.com'.

    As of tmux 1.9a, attempting to create a new session gives an error:

    [$]> tmux new -s a.s bad session name: a.s

    I don't know if this was intentional, but I didn't see it (or anything
    seemingly related) in the changelog.

    Yes, that was changed.

    -- Thomas Adam

     

    Related

    Tickets: #109

  • It was never wise to have periods in session names and now it is forbidden outright. I would possibly be open to a patch that automatically converted them to underscores or something but it might be hard to get it right.

     
    • Kevin ROY
      Kevin ROY
      2014-03-17

      Hi Nicholas,

      I'm not completely aware of the session code but could you explain a bit more why having periods in session names is a bad habit, please?

      I did a little search through the code and I didn't find out a reason to this restriction.

      But maybe i've just missed something new in the changelog (and obviously in the code).

      Thanks for your explanation in advance ;)

      -- Kevin Roy

       
  • Hi. It's because targets use : and . as separators.

    -------- Original message --------
    From: Kevin ROY kiniou@users.sf.net
    Date: 17/03/2014 20:52 (GMT+00:00)
    To: "[tmux:tickets]" 109@tickets.tmux.p.re.sf.net
    Subject: [tmux:tickets] Re: #109 Periods no longer allowed in session names

    Hi Nicholas,

    I'm not completely aware of the session code but could you explain a bit more why having periods in session names is a bad habit, please?

    I did a little search through the code and I didn't find out a reason to this restriction.

    But maybe i've just missed something new in the changelog (and obviously in the code).

    Thanks for your explanation in advance ;)

    -- Kevin Roy


    [tickets:#109] Periods no longer allowed in session names

    Status: open
    Created: Wed Mar 05, 2014 03:19 AM UTC by Xiong Chiamiov
    Last Updated: Wed Mar 05, 2014 11:22 AM UTC
    Owner: nobody

    In tmux 1.8 and earlier, periods were valid in session names.  I found this useful, as I use sessions that map directly to directories on the filesystem, and I have projects named things like 'xiongchiamiov.github.com'.

    As of tmux 1.9a, attempting to create a new session gives an error:

    [$]> tmux new -s a.s
    bad session name: a.s

    I don't know if this was intentional, but I didn't see it (or anything seemingly related) in the changelog.


    Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/tmux/tickets/109/

    To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

     

    Related

    Tickets: #109

    Attachments
    • status: open --> closed