From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11181 invoked by alias); 16 Jun 2015 00:20:52 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35480 Received: (qmail 4576 invoked from network); 16 Jun 2015 00:20:51 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=VizO/vic6D/RyncEAmr5QOv1Jm2k+4e7J1ANK4qsuxo=; b=lI0F0VvuiNImmVq34xZjnGiAqJYiyBmFQgIw154S1iodurDZ+Tat9MpdTmSLNYGjms 6Mr/oAiODy3ORvWYK0wQjDH0XLfZ+ReJ1aTGw97FdV17f3Vsu0dMKFvw/zz9/IWAW3wS UQrdEFMyi9Bpbfc/4tKvAPHNbZGKf6V5fdIcYz6sa9Z9jxtf0qErmMlVxZjjF8bCY4UT qZFJQVdVpmprsSD7QHM4n0cN2PwsQFnxzf53iMQXML64vtpsEPS0qBvo5x5AzV2+xbnd bpWrwjDO3DCQ4t1wMyrfcQhFY4KjKirL0W3YbpPsqqftYqtagwNJHBpDa9075JOtAg77 3J+A== X-Gm-Message-State: ALoCoQkt7xr7neLvwPQJF4Wi015uBipkQ/AkXPsE8vdVeCe7kiTOzNlRzsRw1uWgmx7WpChQY1ai X-Received: by 10.182.230.67 with SMTP id sw3mr26394744obc.0.1434414048056; Mon, 15 Jun 2015 17:20:48 -0700 (PDT) From: Bart Schaefer Message-Id: <150615172044.ZM25490@torch.brasslantern.com> Date: Mon, 15 Jun 2015 17:20:44 -0700 In-Reply-To: <20634.1434406318@thecus.kiddle.eu> Comments: In reply to Oliver Kiddle "Re: bracketed paste mode in xterm and urxvt" (Jun 16, 12:11am) References: <55677AF5.50709@thequod.de> <27004.1433345491@thecus.kiddle.eu> <3098.1433511607@thecus.kiddle.eu> <7701.1433896116@thecus.kiddle.eu> <150609213830.ZM29868@torch.brasslantern.com> <20634.1434406318@thecus.kiddle.eu> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: bracketed paste mode in xterm and urxvt MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 16, 12:11am, Oliver Kiddle wrote: } } So this next attempt uses ZLE_BRACKETED_PASTE_ON/OFF though I'm open to } better ideas. I might have chosen a single two-valued array and require it to either be empty or to have two values (whether "exactly" or "at least" is less important) so that it's harder e.g. to accidentally begin bracketed paste mode and never exit from it. } I've not made them special, just initialised them with a call to } setsparam as that seemed simple enough for the purpose. Is that } reasonable or should they be special? Mostly, variables only need to be special when they have a custom GSU structure, e.g., ZLE_RROMPT_INDENT keeps the internal rprompt_indent value updated because it's accessed frequently (so calling getsparam() is too inefficient), so it is special.