Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] vim: cannot recall command line history
Date: Sat, 27 Jul 2019 11:49:31 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13361@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

New issue by blehel on void-packages repository

https://github.com/void-linux/void-packages/issues/13361
Description: ### System

* xuname:  
  Void 4.19.59_1 x86_64 AuthenticAMD uptodate rrFFF
* package:  
  vim-x11 8.1.1729_2

After upgrading from version 8.1.1635_1, I can no longer recall the command line history of previous sessions with the arrow keys.

### Expected behavior

Pressing `:` and up-arrow recalls the previously typed command lines, including from previous runs of vim, based on the viminfo file.

### Actual behavior

Only the current session's history can be recalled, seemingly because the relevant part of the viminfo file is not processed on startup. The fiIe itself is being read, because the registers and jump list are restored. These items, including the command line history are still being written into it at exit time. 

Interestingly, if I manually read the viminfo file with `:rviminfo! ~/.viminfo`, I get the history back as well.

P.S. I guess this is the commit that deals with this issue:
https://github.com/vim/vim/commit/26b654a5df9414e43734eb4c956b67c331d70a50


             reply	other threads:[~2019-07-27  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27  9:49 voidlinux-github [this message]
2019-07-28  9:06 ` [ISSUE] [CLOSED] " voidlinux-github

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13361@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).