From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27869 invoked by alias); 13 Dec 2016 16:12:15 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22213 Received: (qmail 4513 invoked from network); 13 Dec 2016 16:12:15 -0000 X-Qmail-Scanner-Diagnostics: from mail-vk0-f42.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.213.42):SA:0(-0.0/5.0):. Processed in 1.469021 secs); 13 Dec 2016 16:12:15 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.213.42 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject:cc :mime-version; bh=3hgCcSrAPppw7fit4P13OMRIu6eLBJtddDuu+9UoK6k=; b=OqgUi1uK0es9FOFK98/KN9teiMwo5nYLTWfMnoNwYIkufdRTsZimWrEK6NC5CkRbuz lBWWW94pyyZe03BO8mFpl+QRu63Rph9eYKNfpRgvKiE6//DTR0hJP2DBApZxV57cwHaP MjLPgfVH84giOGkfryAp1pQ2Yo5QOgIsxMHV7wOGl4oZB8g7K6duuAeThGmXjbABaKVO pKlda+jCMnuFhnXHdchHuGYlG8Sk80OFXDxkqGEudvZwgCkV7fb8Pwaqvy52S9cOcCnL +TgP43xMlQLpLvxIW+wj5ERLtd2nZq0ZqydzIZ1QhQHgsHC7LnHV85kwwS0KrzJh2xoZ TEug== 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:cc:mime-version; bh=3hgCcSrAPppw7fit4P13OMRIu6eLBJtddDuu+9UoK6k=; b=cIgPs9YUVN7gIpCysrmTiHDe0XfE9Uk2LwxGUW8YBj4PHBnk96dI1SVO1pKzWrRZHW PohC1RthK6FoinrZ8VXHYyMqdr2n4wJd9MVfAacFhquogHgI93ekji93FIvU7RcrrkCt jj8jQUGsEZg9j6LP9ygMjcbtRAgaUDOTxmO9RpIHjFNlSsavfemmZAJjXV1ZTPM/rtEn hUhNvDwIOU8IcmHoKTr/araNxc+6DtAuxtzOZBwoMTfV8p8wrAc9SIpsExhhPPAIAYM3 hluB26G7W+XnM5RfMTsts0oO/HGKp5PmEvTKwWLWwbmPUjKABrwy92h22I4089k87WdL RLCA== X-Gm-Message-State: AKaTC00DoEsnJC+3W0VItfXCodYvn2WYpskzJjTQ3FaRDb1aEzVoyQshudW970yWwXcdmg== X-Received: by 10.159.41.7 with SMTP id t7mr81405357uat.110.1481645524956; Tue, 13 Dec 2016 08:12:04 -0800 (PST) From: Bart Schaefer Message-Id: <161213081230.ZM21776@torch.brasslantern.com> Date: Tue, 13 Dec 2016 08:12:30 -0800 In-Reply-To: <20161213150101.lgcl6r44gc5b4sia@spiegl.de> Comments: In reply to Andy Spiegl "Howto to print ENTER to zle-buffer?" (Dec 13, 4:01pm) References: <20161213150101.lgcl6r44gc5b4sia@spiegl.de> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: Howto to print ENTER to zle-buffer? Cc: Andy Spiegl MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Dec 13, 4:01pm, Andy Spiegl wrote: } } print -z "command-to-run args" } zle accept-line } } Can zsh be told somehow to "press enter"? If you're doing this in a startup file, you probably want print -S "command-to-run args" command-to-run args That is, explicitly place the command into the history, and then run it directly. If for some reason you really need the command executed within ZLE, you will have to create a zle-line-init widget that will accept the line and then remove or update itself that so it doesn't run it a second time.