I have installed ElScreen using list-packages, and I have the below in the init.el file:
(require 'elscreen)
(elscreen-start)
but then when I open a file file-a.txt, it will only show me the current filename in tab bar. I open a another file file-b.txt, that the tab bar will only show one tab for file-b.txt - file-a.txt is not listed.
Is there any method of showing all open buffers - with the exception of * Messages * and * scratch *?
You're asking if there is a method to show all open buffers: here is a very easy one :D
you see the "Buffer" menu ? Click on it and click on the line of dashes
----------- <--- click here
buffer foo
*scratch*
We can detach the menu like this and have it floating around and staying always on top. You've got your answer !
Now my commentary on elscreen: with elscreen you have to ask to open a new tab with elscreen-create. See http://www.wikemacs.org/wiki/Elscreen for the commands and a discussion about some tweaks, like isolating buffers in their tab or per project
Last notes:
If you never want the scratch buffer:
Automatically closing the scratch buffer
Related
Is there an option in VSCode to limit "navigate back" such that it only takes you back to where you cursor was last in your current file?
This is the current behavior:
(On file A) open method foo
(On file A) open method bar
(On file B) open method baz
(On file A) open method bor
If I navigate back when I am on bor, my cursor will land on baz in file B.
Will it be possible to change this such that I land on bar in file A in stead?
From the issue cited below:
Added a new setting workbench.editor.navigationScope that can be
configured to editor to limit navigation actions such as "Go back"
and "Go forward" to the current active editor group.
workbench.editor.navigationScope
Should be in v1.65.
This functionality doesn't exist, see open issue: Have a history per editor for in-editor navigation.
However, in some cases like your simple example, Cursor Undo ,Ctrl+U, will work as you want. But it is pretty limited. Upvote the issue.
With (menu-bar-mode 0) in my .emacs-file, Emacs (in a terminal) seems to be starting with the menu bar visible, and then within a fraction of a second, the bar disappears.
Is there a way to make Emacs not show the menu bar at all?
No: Emacs first starts by setting up its "frame" (which includes some initial display), then reads the .emacs file. That's why you see this flashing of the menu-bar. Emacs could read the .emacs first, but if the .emacs outputs any message or signals an error, there'd only be stderr to display it, whereas with the current setup, those messages are displayed in the minibuffer and the error can be caught in the "normal" way.
If you're runinng Linux (and I guess any system where Emacs runs in an X server), you can use X resources to tell Emacs you don't want the menu bar. Just put this in your ~/.Xresources file:
emacs.menuBar: off
These resources are used to customize frames appearance and are therefore read by Emacs at the very beginning.
See also:
Emacs manual: Menu Bars
Emacs manual: Table of Resources
man xrdb(1)
I have installed YaSnippet in my emacs. Every time I start emacs, I have to turn on the menu bar manually by M-x menu-bar-mode, how do I load it by default ?
Also strangely the YaSnippet menu shows up the first time the menu bar comes up, however after I move to another buffer and back, I cant see the menu anymore ! How do I get it back without restarting emacs?
The menu bar is loaded by default in emacs. Therefore if you have to turn in on in every buffer it means that you have disabled it in your init file. Remove a line that would say something like (menu-bar-mode 0).
To start menu-bar-mode automatically, just put (menu-bar-mode 1) in your ~/.emacs
I'm afraid your yasnippet problem is outside of my realm of lore :(
I'm working on my .emacs configuration for clojure development.
What I want to happen is whenever I open a file called "project.clj" if there is no open buffer called "swank", split the window first horizontally then split the right side vertically. Then from the project.clj buffer run (clojure-jack-in) to start the REPL and (shell) to load a bash shell. When all of this is done I'd like the project.clj file to be in the left window, the shell to be in the top right window, and the REPL to be in the bottom right window.
Also if there's a way to get speedbar to open in a specified window rather than in a new frame, that would be awesome.
I guess my question is: is there a way to specify which window new buffers are opened in?
Ok, how about this answer via ibuffer or via grid-files-sq or GridLayout and (more unrelatedly) desktop remembering suggestions
I'm a new emacs user using emacs for the awesome org-mode. I have links to all my org files at the top of my pages but everytime I click a link it splits my window, so I only have half of the screen estate available. How do I set it so that emacs does not split the window horizontally but rather opens up a new window for my links?
I'm assuming you mean you want to open the link in a new frame. (Emacs terminology is a bit different from other GUI apps, because Emacs predates X11. What would be called a "window" in other apps is called a "frame" in Emacs, because "window" already had a specific meaning in Emacs, and was used in the names of lots of functions.) What's happening now is that you have a frame containing one window, and Emacs is splitting that window to form two windows.
You need to customize org-link-frame-setup to use find-file-other-frame instead of the default find-file-other-window.
You can do this by typing M-x customize-variable <ENTER> org-link-frame-setup <ENTER>. Click the Value Menu next to find-file-other-window and select find-file-other-frame, then click Save for future sessions.
One option is to tell Emacs to never split windows, which can be done like so:
(setq same-window-regexps '("."))
This will keep your window from splitting, and then you use your regular commands to switch buffers to get back to what you were looking at.
This is as opposed to what it sounds like you were asking for, which was new frames, which IMO doesn't really help if you have limited screen real estate because you're now having to switch frames (graphical windows).