This is an opinionated repo that contains our bash, vim and other (.) files.
This is an opioniated repo for Kishorekumar Neelamegam.
We have recorded our setup just so we dont forget how to bring back the workstation when there is a crash
My primary OS is either
(or)
FreeBSD Please refer the section below for the status of the migration.
(or)
Chromebook eventually - with everything on cloud 😄
At the moment on ArchLinux + Gnome.
Archlinux is much faster but eventually will move to FreeBSD or OpenBSD for OCaml dev.
This key board is much better than Logitech K380 where these keys are mapped with the Fn + combination, but in Rapoo they are available directly
- PrntScrn
- Home
- End
- Page up
- Page down
Believe Logitech must learn from Rapoo guys.
The K380 cheat sheet is available for referencing the shortcut keys mentioned below.
- PrntScrn
- Home
- End
- Page up
- Page down
As a (type of user), I want to (perform some action) so that I (can achieve some goal/result/value).”
Scenario #1: User submits feedback form with the valid data
*Given I’m in a role of logged-in or guest user
When I open the Feedback page
Then the system shows me the Submit Feedback form containing “Email”,“Name” and “Comment” fields which are required
When I fill in the “Email” field with a valid email address
And I fill in the “Name” field with my name
And I fill in the “Comment” field with my comment
And I click the “Submit Feedback” button
Then the system submits my feedback
And the system shows the “You’ve successfully submitted your feedback” flash message
And the system clears the fields of the Submit Feedback form*
Upon install, what tweaks are needed to bring my workstation up to the state for dev.
- Trizen
- VIM & Vundle
- Node
- Rust
- OCaml
- Flameshot
- Libreoffice
- Brave
- VLC
- Docker
- Nautilus extensions
- 1Password
pacman trizen
trizen powerline-go-bin
trizen powerline-common
trizen powerline-fonts
This is recommended and have moved to this approach.
The install from release source is great, but have experienced slowness (un sure why) on the latest builds
trizen vim
ℹ️ Install Vundle(plugin manager)
https://github.com/VundleVim/Vundle.vim
ℹ️ vim-devicon fonts
trizen ttf-nerd-fonts-symbols
ℹ️ Search using ripgrep
trizen ripgrep
ℹ️ Clipboard (wayland)
trizen wl-clipboard
vim --version | grep clipboard
If you see +clipboard
or +xterm_clipboard
, you are good to go.
If it's -clipboard
and -xterm_clipboard
,
you will need to install
trizen gvim vim
To verify a mapping for CTRL-C and CTRL-V
::verbose map <C-V>
Note, as of this writing 20.x was the latest, but replace the wget
https
url with the latest by visiting Node.js to grab the latest LTS
cd ~/bin; wget https://nodejs.org/dist/v20.11.0/node-v20.11.0-linux-x64.tar.xz
tar -xvf node*.tar.xz; mv ~/bin/node* ~/bin/node
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
trizen postgresql-libs
trizen ocaml
cd ~/bin; wget https://github.com/ocaml/opam/releases/download/2.1.5/opam-2.1.5-x86_64-linux
mv ~/bin/opam* ~/bin/opam
opam init
opam install dune
trizen flameshot
The app indicator extension is gnome is needed.
trizen gnome-shell-extension-appindicator
trizen libreoffice
trizen brave
trizen vlc
trizen docker
trizen docker-buildx
trizen docker-compose
trizen nautilus-open-any-terminal
12 1Password
curl -sS https://downloads.1password.com/linux/keys/1password.asc | gpg --import
trizen 1password
Compose Ansible playbook to configure the workstation during the OS installation.
The objective is to have the script operate solely locally without running any daemons or agents.
⚓ Perhaps leverage ChatGPT to generate the script.
trizen -S ansible
ansible --version
I have backed up my files in a standard repo. Hence I will apply both the GDrive private + the public files.
Use the Gnome online account and connect the GDrive account.
3 Clone indykish/dotfiles.git
git clone https://github.com/indykish/dotfiles.git
4 Execute the playbook
cd dotfiles
ansible-playbook -K workstation_setup.yml
The current status of my FreeBSD migration is as follows:
I haven't had much luck with a full switch yet. I am not inclined to work using an emulation layer.
I prefer native solutions or workarounds. However, the list below is still a work in progress:
Workarounds for Teams and Zoom can function as additional workstations, running either Windows or Linux or connecting via mobile.
- Slack (Completed)
- Zoom (Incomplete)
- Teams (Incomplete)
- Vim (Completed)
- OCaml (Incomplete)
- Rust (Incomplete)
- Perl (Incomplete)
- Typescript (Incomplete)
- Dry run ui (Incomplete)
- Dry run coreapi/auth (Incomplete)
- Dry run python, perl scripts (Incomplete)