New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ivy starts by showing a single line #229

Closed
brabalan opened this Issue Sep 15, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@brabalan

brabalan commented Sep 15, 2015

Since last update, each time I use ivy I only see a single minibuffer line until I start typing something. The problem is that I don’t know what is currently selected, so I cannot just hit enter to use it.

Here are a couple screenshots.

counsel-M-x
screen shot 2015-09-15 at 08 32 39

switching buffers
screen shot 2015-09-15 at 08 33 40

Is there an option that has changed for the initial minibuffer size?

@abo-abo

This comment has been minimized.

Show comment
Hide comment
@abo-abo

abo-abo Sep 15, 2015

Owner

Can't reproduce. Please update to the latest MELPA version, and test with various Emacs versions if you can.

Owner

abo-abo commented Sep 15, 2015

Can't reproduce. Please update to the latest MELPA version, and test with various Emacs versions if you can.

@brabalan

This comment has been minimized.

Show comment
Hide comment
@brabalan

brabalan Sep 15, 2015

I’m using the current MELPA version.

I was able to reproduce it with a “minimal” configuration (using package-initialize): this seems to happen only when a second frame has been created.

This is what I did. With this init.el:

(setq emacsd-dir "/Users/schmitta/.emacs.d/")
(setq package-user-dir (concat emacsd-dir "elpa"))
(package-initialize)

I start emacs

% open /Applications/Emacs.app -n --args -Q -l ~/tmp/init.el

I then do M-x ivy-mode, C-x 5 2, M-x and I observe the problem.

brabalan commented Sep 15, 2015

I’m using the current MELPA version.

I was able to reproduce it with a “minimal” configuration (using package-initialize): this seems to happen only when a second frame has been created.

This is what I did. With this init.el:

(setq emacsd-dir "/Users/schmitta/.emacs.d/")
(setq package-user-dir (concat emacsd-dir "elpa"))
(package-initialize)

I start emacs

% open /Applications/Emacs.app -n --args -Q -l ~/tmp/init.el

I then do M-x ivy-mode, C-x 5 2, M-x and I observe the problem.

@abo-abo abo-abo closed this in 435f2b6 Sep 15, 2015

@abo-abo

This comment has been minimized.

Show comment
Hide comment
@abo-abo

abo-abo Sep 15, 2015

Owner

Thanks, I was able to reproduce with many frames (I always use just one). I don't know the reason for this strange behavior, I only added a work-around that checks the number of frames.

Owner

abo-abo commented Sep 15, 2015

Thanks, I was able to reproduce with many frames (I always use just one). I don't know the reason for this strange behavior, I only added a work-around that checks the number of frames.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment