Bash Editor
Nichol Sadlon
I am currently using vim editor on Git Bash terminal running in a Windows machine, but I want to switch over to Emacs editor. It is returning bash: emacs: command not found . Do I need to install the Emacs? If true, what command do I use, and what could be the general soulution?
There are a couple of ways to configure Bash. You can use a local configuration file, such as /home/yourhomedirectory/.bashrc, which only changes the default for your user account and not for other users on the same system. I prefer to make these types of changes global, which basically means my personal account and root. In this second case, you can create your own configuration file and place it in the /etc/profile.d directory.
A heads up. Maybe? I created the .sh file in profile.d as described except that I replaced "vi" with "vim". When I restarted the computer it would not progress login from gui - each attempt would just return me to the login page. I found that I could login from the terminal where I got a complaint from bash about -o vim. I removed the file from profile.d and graphic login was restored. I have not corrected the commands to "vi" and tried again but will. Just wanted to warn others of the possibility
I'm running bash, and my /.inputrc contains set editing-mode vi. This allows me to edit my command line using vi-like behaviour. And I can press v in normal mode to enter the full-fledged vi-editor, if I need full power to edit the command.
The only problem is that when I exit, the command executes right away. I would rather continue editing on the command line so that I can take advantage of bash's completion features. I can't do that when I'm in the vi editor. Is there a way to avoid automatically executing the edited command upon exiting vi?
you need to let home-manager manage your bash config files.
-manager/blob/223e3c38a13fb45726c7a9d97e2612ae53ab4f98/modules/programs/bash.nix#L199
this is where the injection of the home-manager session-variables should get injected.
Then the hm-session-vars file is included in .profile (which is just run once when your graphical interface first starts). So either you can source .profile every bash, or you ask bash to source that file for you. I just do that by replacing the above bash configuration with:
Thank you, glenn! Yeah, the run button execute the code. However, I don't know how to use other command like" $env; $export variable=xxx"... and etc. I'm beginner and all commands I have are bash orientated... so prefer to has bash environment at least for now... Anyway, thanks for your inputs.
Bash Console was an option which could be selected at the very first time when you open a python file. I used bash for a while till I accidently clicked the 'run' button which seems go back to its default setting now...
df19127ead