all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Daniel Gröber" <dxld@darkboxed.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] term/rxvt: Enable bracketed paste mode
Date: Tue, 03 Mar 2020 15:22:24 -0500	[thread overview]
Message-ID: <jwv8skhw646.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20200302020046.120515-1-dxld@darkboxed.org> ("Daniel Gröber"'s message of "Mon,  2 Mar 2020 03:00:46 +0100")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/x-markdown; coding=UTF-8, Size: 728 bytes --]

> rxvt-unicode uses the same escape sequences as xterm so just re-use
> the xterm function to enable it.
>
> The xterm-rxvt-function-map keymap already has
>
>     (define-key map "\e[200~" [xterm-paste])
>
> so we're already handling the paste sequence and only need to enable it.

I don't have rxvt to test, but the patch looks good.  What I wonder if
whether it would make sense to use even more of `terminal-init-xterm` in
rxvt.el.
E.g. focus-tracking, frame-title?

I also see that terminal-init-xterm tries to detect when it's been
accidentally called in rxvt, and in that case it still keeps most of
terminal-init-xterm intact.  Apparently, this is right for
bracketed-paste, but what about the rest?


        Stefan




  reply	other threads:[~2020-03-03 20:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02  2:00 [PATCH] term/rxvt: Enable bracketed paste mode Daniel Gröber
2020-03-03 20:22 ` Stefan Monnier [this message]
2020-03-04  0:46   ` [PATCH v2 0/3] Improved rxvt support dxld
2020-03-04  0:46     ` [PATCH v2 1/3] term/rxvt: Enable bracketed paste mode dxld
2020-03-04  0:46     ` [PATCH v2 2/3] term/rxvt: Add window title support dxld
2020-03-04  0:46     ` [PATCH v2 3/3] term/rxvt: Add terminal-init hook dxld
2020-03-08 18:13     ` [PATCH v2 0/3] Improved rxvt support Stefan Monnier
2020-03-08 19:33       ` Daniel Gröber
2020-03-08 23:20         ` Stefan Monnier

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=jwv8skhw646.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dxld@darkboxed.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.