From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 22051 invoked from network); 28 Jul 2020 12:38:58 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 28 Jul 2020 12:38:58 -0000 Received: (qmail 6454 invoked by alias); 28 Jul 2020 12:38:48 -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: List-Unsubscribe: Sender: zsh-users@zsh.org X-Seq: 25007 Received: (qmail 27369 invoked by uid 1010); 28 Jul 2020 12:38:48 -0000 X-Qmail-Scanner-Diagnostics: from mail-wm1-f52.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25884. spamassassin: 3.4.4. Clear:RC:0(209.85.128.52):SA:0(-2.0/5.0):. Processed in 1.732115 secs); 28 Jul 2020 12:38:48 -0000 X-Envelope-From: luomat@gmail.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.128.52 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=MPd7PQEVTXtAg3utVfiPiz7iVv+t9m1U745oQKf/P3s=; b=cOsERt5fZUWX3kz7QiBfCVqus8w1Aa47VBxLbH8LF7NK7DQyU/7A7OvgaQBQPu8at3 Fu3gpUYFPIbMuBXGw77CaCxxtaF405ER7d6GsuPkEJ7+nvdv2CIqXMp74IbCsNAEef0k Sj8krjobsPyZ1i6t/ayzfaRGivtECtJiNFyLdeGn5/BTUxQ8cYO/TcvkFIqeDK87h1Rm W4JjZAhjACaaZgq6Fyfe60efhTmREn52yr4cEaZTpATTddUTu7mnQh4+aT3CDLEG0Bns 1rglehFTM/CEXXhwQOvCcdjR+AvPeysJtXI9PkzUPzySMt3z1k4gI35iwHqVLI2iAYOm GMKg== X-Gm-Message-State: AOAM531+WhK1BDaxsoCgmbaNXOJKhnsvFwswOwNhqzyz2Wv7QPwbwg0m kGIaZfHAhYJwx9kg+DjMnmt+SMocXp9ZJBOwKRFWEuU3 X-Google-Smtp-Source: ABdhPJwI/giqAakQPvV6g9YnfHxoVHUHOl7WJ5k8Um+Hn4GIV2wCWQZlxqhHlVILMfIhpRCsAPewKv6O4C61EvgwSqk= X-Received: by 2002:a1c:19c6:: with SMTP id 189mr3741610wmz.98.1595939891524; Tue, 28 Jul 2020 05:38:11 -0700 (PDT) MIME-Version: 1.0 From: TJ Luoma Date: Tue, 28 Jul 2020 08:37:35 -0400 Message-ID: Subject: up-arrow for history 'broken' after ssh To: Zsh MailingList Content-Type: text/plain; charset="UTF-8" I have run into this before, and I know it's a relatively simple fix, but it has been a few years and my Googling has not turned up the answer. I have my zsh history set up such that if I start typing a few letters and then press the 'up arrow' it will only show me history items which match the letters I have already typed. However, when I ssh from my Mac to a Linux machine (which has a different zsh setup), and then exit ssh, my 'up arrow' goes back one at a time, regardless of whether or not I have typed anything first. Can someone remind me how to fix this? Thanks! Tj