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=MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 12144 invoked from network); 27 May 2020 04:26:53 -0000
Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2)
  by inbox.vuxu.org with ESMTPUTF8; 27 May 2020 04:26:53 -0000
Received: (qmail 1497 invoked by alias); 27 May 2020 04:26:43 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
List-Unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
X-Seq: 45928
Received: (qmail 22124 invoked by uid 1010); 27 May 2020 04:26:43 -0000
X-Qmail-Scanner-Diagnostics: from mail-oi1-f180.google.com by f.primenet.com.au (envelope-from <schaefer@brasslantern.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.102.3/25821. spamassassin: 3.4.4.  
 Clear:RC:0(209.85.167.180):SA:0(-1.9/5.0):. 
 Processed in 0.695126 secs); 27 May 2020 04:26:43 -0000
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.167.180 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:references:in-reply-to:from:date
         :message-id:subject:to;
        bh=e34pQIGn7AXIRiBbQ6uaw/uihQ0DY2v74l0t2A++5yI=;
        b=uMHxzTkLQpuTMDgL5JCJwP2M5zQ0YmuTaFBD/TqEmliogARPZLfF/wLhcw0Lk7Iv2q
         CydIDqhklMAJeJFskEdW9RJxVTj5jsAAkRnhjoZEZ2kRiz9AFMtIFEDW4uXdGd8Mii6s
         WD17l0RB0UPs09D7t1idZQFuENXvfZ6ze+vSllh6jUVV1Xi9afqJJAOIkhPUgi4gjYiR
         UoBOWyaSkgUTSAHt99+LvC/tC695lv4ho7GHtjmkdlBffEJkCGuefe2XQ36V4eV2YCCD
         Ozo6lgBNYruF/h/b3mSqx4BUbtOfeBTDa3BeXLxVKQjXRbr7lMmXgi21uaJwHp6dN59O
         OiAg==
X-Gm-Message-State: AOAM530GTxOVp6ktrODfkSSam8kzYw22CLTQjS8j03ZZ5j7zlMMACUNc
	vIdCb7MtFDcVcF9/MYZEd7sSci1j61sHdoDJh0NPZjk6P4KdVg==
X-Google-Smtp-Source: ABdhPJzrLoyEOTSRxc1zNRgC/hNS83lcXcaJrRstEJYCYiiiM/8/Yk8kCjFa/913noACEcFCK1np/upymbhdsPM5RQA=
X-Received: by 2002:aca:c590:: with SMTP id v138mr1530394oif.132.1590553568750;
 Tue, 26 May 2020 21:26:08 -0700 (PDT)
MIME-Version: 1.0
References: <CAH+w=7ZdH+J4nfgfigjm2b_gQQfHMkKhhTCycb-SOp9YwNXSbA@mail.gmail.com>
In-Reply-To: <CAH+w=7ZdH+J4nfgfigjm2b_gQQfHMkKhhTCycb-SOp9YwNXSbA@mail.gmail.com>
From: Bart Schaefer <schaefer@brasslantern.com>
Date: Tue, 26 May 2020 21:25:57 -0700
Message-ID: <CAH+w=7bCUavuPzMKvJtu0mvrp8HuzGUdpkXbF7ZkxTWWkPx3QQ@mail.gmail.com>
Subject: Re: zed-set-filename breaks zed keymap?
To: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset="UTF-8"

On Tue, May 26, 2020 at 8:30 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> I discovered that even with plain "zed file" after entering the file
> name into read-from-minibuffer, ^X^W no longer works to exit from zed,
> and a bare return DOES exit it.

The documentation for zed-set-file-name seems contradictory as well.
In the first paragraph it says:

     ... because of zed's rebindings you will have to type ^j at the
     end instead of the return key ...

but then the second paragraph says

     While zed-set-file-name is running, zed uses the keymap
     zed-normal-keymap, which is linked from the main keymap in effect
     at the time zed initialised its bindings.  (This is to make the
     return key operate normally.) ...

The return key does not in fact "operate normally" during
zed-set-file-name, but something else strange is going on with the
keymaps.