Giter VIP home page Giter VIP logo

dotfiles's People

Contributors

eyuelt avatar

Watchers

 avatar  avatar

dotfiles's Issues

Install Vundle in setup script

The setup script doesn't currently install Vundle, so when you open vim after running the script, you get a bunch of errors and all of the plugins are missing.

Show computer name in prompt

Since I hop between different machines, It would be nice to show which computer I'm on in the prompt. The problem is that the hostname is pretty ugly on some of these machines. I could either change the computers' hostnames or just have a $NICKNAME variable that I set in my .localrc file.

Allow setup script to be run without sudo

Add a nosudo option to the setup script so it can be run on systems where the user doesn't have sudo access (minus the functionality that actually requires sudo).

Vundle.vim folder in wrong place

When the setup script is run, the Vundle.vim folder is being installed into the current directory, rather than in .vim/bundle/. This started around the time when I added the $VUNDLE environment variable, so I think there's an issue with that.

Fix sudo alias

Since sudo is aliased, I get issues when I try to use it with options. Since the alias is just to change the env, I only want it to take effect when sudo is followed by non-option arguments.

So in these cases:

  • sudo ./script.sh
  • sudo vim foo.txt

but not in these cases:

  • sudo -k
  • sudo

I'm thinking of doing this by using a wrapper around sudo instead of an alias.

Make reverse-i-search only work if line is non-empty

Since with reverse-i-search, the cursor stays at the position where it is doing the search from. This means that when the line is empty and I press up to go to the previous command, the cursor stays at the beginning of the line. The expected behavior in this situation is for the cursor to move to the end of the line.

Before pressing up:
screenshot 2014-02-27 23 44 38

After pressing up:
screenshot 2014-02-27 23 40 44

The best solution to this is probably to only do reverse-i-search when the line is non-empty and to have it do its default behavior otherwise.

History for partial lines in command line

I want to be able to start writing a line in my shell, then if I press up, be able to go through all of the lines in my history that start with what I've written. For some reason, I thought I already had this feature but I guess not.

Run zsh when script finishes

Call exec zsh at end of script to switch to zsh. This isn't necessary if we're on a mac and we relaunch Terminal to set the default theme.

$DOTFILES doesn't work when using sudo

Environment variables aren't preserved when using sudo. So using vim with sudo spits out an error because my vimrc uses the environment variable $DOTFILES, which is exported by my zshrc.

screenshot 2014-03-18 05 01 34

One solution may be to add the $DOTFILES variable to the sudoers config file, like this stackoverflow answer suggests. Though I don't really like the idea of putting this, or any other non-system-wide environment variable, in a global config file.

Remap Caps Lock key to Ctrl

I'm not sure if there's an easy way to do this programmatically, but if there is, it'd be nice to have it done automatically from the setup script.

Install Vundle even with nosudo

Vundle and vim plugins should still be installed even if the --nosudo option is used, as installing it doesn't require sudo access.

Clean up installation stuff

Mainly just clean up the install script. Also, the setup script currently tries to install zsh, this should be left to the install script.

Define DOTFILES var during setup script

The osx/set_default_terminal_theme.sh script depends on the DOTFILES var, however system/envvars.symlink is not yet sourced.

For the script/setup script, to get around this, we defined DOTFILES locally. Maybe we should just export it there. Otherwise we'll need to treat envvars specially and source it during the setup script, unlike the other symlink files.

Besides, envvars contains vars that we want globally defined in general. All we need is for a few vars (DOTFILES and maybe VUNDLE) to be defined during the setup script. So there's no need to source the whole envvars file and load all of those vars.

Make code directory if it doesn't exist

The code directory is specified by the $PROJECTS env variable in envvars.symlink. The setup script should somehow be able to access this variable and run mkdir -p $PROJECTS. Maybe the setup script could just source envvars.symlink before doing anything. This seems kind of weird, but it's better than redeclaring each variable at the top of the setup script.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.