emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: patch: ob-screen: don't change user-specified session name [9.3.7 (9.3.7-12-g5d6868-elpaplus @ /home/kdm/.emacs.d/elpa/org-plus-contrib-20200706/)]
Date: Tue, 14 Jul 2020 01:01:27 -0400	[thread overview]
Message-ID: <871rle666w.fsf@kyleam.com> (raw)
In-Reply-To: <874kqgsm1o.fsf@gmail.com>

Ken Mankoff writes:

> ob-screen prepends "org-babel-session-" to the user-specific screen
> name for some reason. I suggest this is not necessary nor optimal. One
> of the key points of 'screen' is that you can detach and attach from
> elsewhere. The name of the session is an important part of this
> process, and changing the user-chosen name complicates this. I note
> that in the other babel :session names I use (shell, Python,
> jupyter-python, etc.) the :session name is not modified.

Sounds reasonable to me.  Could add a commit message and NEWS entry to
the patch?

  reply	other threads:[~2020-07-14  5:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 16:14 patch: ob-screen: don't change user-specified session name [9.3.7 (9.3.7-12-g5d6868-elpaplus @ /home/kdm/.emacs.d/elpa/org-plus-contrib-20200706/)] Ken Mankoff
2020-07-14  5:01 ` Kyle Meyer [this message]
2020-07-14  5:02   ` Kyle Meyer
2020-07-15  3:09     ` Kyle Meyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rle666w.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).