Search results for query: .shrc

...for blackhole detection (usually ~1200 or 1440) net.inet.tcp.pmtud_blackhole_mss=1536 kern.ipc.somaxconn=1280 hw.snd.default_unit=9 /home/x/.shrc # .shrc - bourne shell startup file # file permissions: rwxr-xr-x # umask 022 # some useful aliases alias h='fc -l' alias j=jobs alias...

Placing the command at the end of the .shrc did the trick – I did not need to comment out the other key bindings. Thanks!

I've found a PR about this: 280889 Ed Maste's comment explains it: And Gert Doering's comment:

I think I have experienced what you've told, what worked for me was to put that line in very below of .shrc file.

The default .shrc in a fresh FreeBSD install contains the command set -o vi (which is commented out). Activating this and starting a new shell leads to unstable bevaviour when editing commands – neither standard movement commands nor vi commands work reliably. But when executing set -o vi...

The point is that they've changed from the default and you can do your own investigation if that's not expected. There are other tools like tripwire and mtree that can give you something that you check before making changes and then log the changes. One of the really helpful thing about using...

...much has to modify /etc/passwd, master.passwd and group, to create user accounts. Most users (including root) are expected to edit .cshrc or .shrc to their taste. The IDS functionality really should ignore those changes. On the other hand, the fact that permissions/ownership for /root...

...but should have SHA256 hash 3f8f2a402ed4f114c317babcd655f47eefaf3d938fc9d5f935d9e379964e74df. /root/.shrc has SHA256 hash fa471312b79e5632ac62513c03478be2398435c1ffba1757ff6a9d7db440d8e3, but should have SHA256 hash 134484e68f3a6c72134980d2d086fc884f5e2419c35f07b0ea4d2fab7e33a59a...

...) then setenv EDITOR vim alias vi vim else setenv EDITOR vi endif You could do something similar with ~/.shrc or some other config file appropriate for your preferred shell. I also set the EDITOR variable, that's useful for vipw for example, or for merges during...

I had forgotten that Bourne shells can be color coded (as of 14.0). An internet search led to https://forums.freebsd.org/threads/the-bourne-shell-prompt-color.85914/ https://forums.freebsd.org/threads/colorize-your-bsd-shell.85458/post-630235

...15.0 (maybe 14.3 as well, I haven't tried yet). Watch the following video where the poster colourises his prompt under /bin/sh using his ~/.shrc. I haven't checked the sh source code for recent changes but I'm assuming that improvements to /bin/sh are being made with each release. Especially...

two examples, cat /home/x/.shrc # Function to safely prepend a directory to PATH if it exists and isn't already there path_add() { if [ -d "$1" ]; then case ":$PATH:" in *":$1:"*) ;; # Already in PATH *) PATH="$1:$PATH" ;; esac fi } export...

two examples, /home/x/.shrc # Function to safely prepend a directory to PATH if it exists and isn't already there path_add() { if [ -d "$1" ]; then case ":$PATH:" in *":$1:"*) ;; # Already in PATH *) PATH="$1:$PATH" ;; esac fi } export PATH=""...

...that specific flags print by means of environment variables. So, a nifty workaround for your case would be to set in your ~/.profile or ~/.shrc: export UNAME_v="$(uname -v) $(uname -KU)" and then use uname -a (since it includes -v flag). 2) Create your own one-line shell-script (myuname)...

You realize that the whole point of this thread is to wean ourselves off Xorg and related stuff like ~/.xinitrc... and that KDE plans to go Wayland-only pretty soon. And BTW, SDDM now works to launch both Xorg and Wayland sessions for KDE, I mentioned that earlier in this thread. And now for...

...line. I know this isn’t what everyone seeks for a stable desktop environment but it works for me. From here I launch the de with the following commands sudo kldload i915kms # my specific GPU driver . ~/.xinitrc # you can alias these commands at ~/.shrc # I set mine to 1. driver and 2. kde

...of the [+] key. But I'm no really sure what you are suggesting. Do mean something in ~/.profile? Do I need to make this change in my ~/.shrc and have no idea what it's for Other solutions I have come across talk about making changes within emacs's configuration files or within...

Dear SirDice : i have used sh echo $SHELL /bin/sh thanks. ok. i know that . i need to modify .shrc file . thanks. all done... other question. i have used the sh as shell...why i still have .cshrc in my home folder ? thanks.

.shrc export COLORFGBG="15;0" export COLORTERM="truecolor" export...

...be executed automatically. How to install it: Install the required port textproc/fzy Then copy the function history_command into the file ~/.shrc or ~/.kshrc, pick your poison. To trigger the shell history this is what I've put in ~/.{kshrc,shrc}: HISTFILE=~/.sh_history # for sh...