I employed the 'Ocean next theme' on alacritty terminal Color schemes · jwilm/alacritty Wiki
Upon starting doom-emacs from terminal (tmux new -s 'main'),
the identical commands emacs -nw display various theme.
I want the one above.
It's tricky that if start a new tmux session with other name saying 'focus',
They display the same themes
Restart the machine multiple times,
my desired theme appears on 'main' session to the above window.
What's the problem?
Your setup has too many layers:
Terminal->Tmux ->Emacs.
Try just running emacs without tmux (emacs has all the tmux goodies integrated) or better run the GUI emacs directly (themes will be in 100% full potential).
BTW, emacs GUI is not like GUI Vim. It's the total package if you run it with exwm.
Take out all decorations (scrool bar menu bar etc..) and it will look like a terminal app except with access to thousands of packages that cannot run in the terminal mode because of limitations.
Once you use it this way. There is no coming back.
My .xinitrc has one line exec emacs (keep in mind you can run firefox inside emacs)
Related
I am using the remote-ssh extension with a (remote) bash as integrated terminal in Visual Studio Code September 2021 release.
When I use the scroll wheel in the integrated terminal, I move through the bash command history (like if I were pressing the up/down arrow keys). Furthermore, there are no scrollbars in the terminal so I am not able to see the text that does not fit in the current viewport.
Is there any way I can use the scroll wheel to actually scroll the content of the integrated terminal window? If I remember correctly, with previous versions of the program I was able to do exactly what I am asking.
The support page https://code.visualstudio.com/docs/editor/integrated-terminal does not say anything about this.
I have another question: is there a place with a comprehensive list of settings for the integrated terminal?
Details:
Version: 1.61.0 (user setup)
Commit: ee8c7def80afc00dd6e593ef12f37756d8f504ea
Date: 2021-10-07T18:13:09.652Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043
Microsoft remote-ssh: version v0.65.8
The issue being described here is the "alternative screen buffer" which causes the scroll wheel to act as arrow keys, scrolling the shell history rather than the window.
If you execute a command (such as vim) that puts you in the "alternative screen buffer" but doesn't put you back when it exits, you can switch back from the alternative screen buffer with:
$ echo -ne '\x1B[?1049l'
# or, if you don't want to memorize that:
$ tput rmcup
If you really want to disable alternate screen buffer switching, which could cause other apps to behave very differently than you're used to which rely on the alternate screen buffer, you could create a new terminfo entry that removes the smcup and rmcup capabilities, which enables this capability.
For example, if you're using xterm-256color, you can create a xterm-256color-noalt terminfo entry like this:
$ infocmp xterm-256color | sed \
-e 's/^xterm-256color/xterm-256color-noalt/' \
-e 's/[rs]mcup=[^,]*,//' \
>xterm-256color-noalt.ti
$ tic xterm-256color-noalt.ti
Then, set your TERM to xterm-256color-noalt:
$ export TERM=xterm-256color-noalt
But, this is a bit more drastic and, like I said, could cause other apps that depend on alternate screen buffer capability being available in the terminal to misbehave or at least behave in ways you don't expect.
CTRL+A then ESC will allow you to use the wheel to scroll up/down
Press ESC to cancel it and get back to the normal wheel functionality.
This had me so frustrated too. After a little trial-and-error, I felt so stupid when I figured out my problem: I was using the WRONG terminal type.
In the terminal "section" at the bottom of VSCode are the tabs: PROBLEMS, OUTPUT, DEBUG, TERMINAL. In the TERMINAL tab, there's a drop-down on the right for terminal type: "tmux" and "JavaScript Debug Terminal" have the awful behavior described above; choose "bash" instead!! "bash" behaves like a proper Bash Linux terminal.
The vim version has a ++close option that automatically closes the terminal when the job terminates, but since the NeoVim terminal came first it doesn't have that feature.
I need this because i am trying to run programs directly from vim, but i regularly make
curses applications which the popup window you get from :!python % can't handle, so i need the terminal window.
I am using NeoVim on arch linux if that's relevant.
I'm trying to walk through the Parenscript library to see how it renders, i.e. what actually happens when you make a (ps... ) call.
Ideally, I'd use VSCode to set breakpoints and watches and step into all called functions. There doesn't seem to be any lisp debugging extension in the VSCode marketplace.
Right now, I'm loading sbcl in a terminal window in VSCode and have command-shift-A bound to Terminal: Run Selected Text In Active Terminal, so that anything I write in the editor can be executed in sbcl.
Is there a way to set up the VSCode environment so that I can have access to debugging tools like watches and step-into?
I have been really enjoying having emacs load as a daemon when I login and using emacsclient -c to pop open an emacs window superquick.
However, I often have multiple emacs windows open at a time. Each one is dedicated to a particular project. Before I used emacsclient each of these emacs windows would be independent of the other, but now, they share the same set of buffers.
How can I continue to use emacsclient, but have the windows act independently?
I can't figure out why this isn't easy to find on Google, but after searching for about 10 minutes, I just decided to give up and post here.
The subject basically says it all. I'm running MinTTY as a cygwin terminal on a Windows XP desktop. All I want to do is have emacs open up in a new window rather than inside my terminal. What would be best is a switch for this, so I could toggle it depending on my current needs. This seems like something that would be useful to a lot of people, and I know I've done it before on Linux boxes, so I imagine there must be a way to do this in cygwin too. Anyone know how?
Just start a new mintty, telling it to invoke emacs:
mintty emacs
There are a couple of scenarios that you might clarify:
Running the cygwin version of emacs within a standard windows environment will call emacs within the current shell
If the Cygwin X-Windows server (i.e., “XWin Server”) has been started and the DISPLAY environment variable has been set in the mintty terminal (e.g., export DISPLAY=":0"), calling emacs will start it in its own window.
running the Windows version of emacs within the cygwin terminal should launch the new frame you are seeking.
If you want a separate emacs 'window', you would be best served by installing the Windows native version of emacs (I use the gnu emacs precompiled binaries), and calling it from the cygwin terminal.