Expectation:

Given I am a person who wants to install dotmatrix
When I run the bin/install script after cloning the repo
Then I should be able to run vim and have Plug installed

Actual Result:

Plug is neither installed or checked for, so the installation of dotmatrix causes vim to spit out a ton of errors related to the missing commands.

We could either run the curl command automatically in the setup script, or we could have the script warn that Plug is missing. Personally I think that installing it is nicest, but it will need to check for the file presence regardless of which path we decide on so I'm open to suggestions otherwise.

Hi guys,

Love Dotmatrix, I forked it and created a new version of my own but still use all the base you created. I have a question I use mux to start tmux but I was reading through the hr mux command and saw this comment:

The above will create a tmux session named after the directory you're in and create a few useful default windows with a sensible layout.

Although I seem to always just get a single window layout with the title "code".

I see there are some lines around

mux_file="$directory/.mux"
[ -f $mux_file ] || mux_file="$HOME/.mux"
[ -f $mux_file ] || mux_file="$_HR_SHARE/mux-init"

and
name=$name source $mux_file

Could this be why? Is this something that I need to create or that maybe should be added to dotmatrix?

(I don't have a .mux file in my home directory)

After installing tmux 2.5, the following errors occur:

invalid or unknown command: bind -t vi-copy y copy-pipe 'reattach-to-user-namespace pbcopy'
invalid or unknown command: bind -t vi-copy v begin-selection
invalid or unknown command: bind -t vi-copy V rectangle-toggle
invalid or unknown command: bind-key -t vi-copy WheelUpPane halfpage-up
invalid or unknown command: bind-key -t vi-copy WheelDownPane halfpage-down

As a workaround, for those using macOS and homebrew, you can revert back to a previous version of tmux by first seeing what versions you had installed: brew info tmux and then switching: brew switch tmux $VERSION.

Running the following command has no output:

hr battery

System: 2017 Macbook Pro 15"
OS: OSX Mojave 10.14.6

Expected Behavior:

Given a hung rails server
When I run freethousand
Then it kills the process running my rails server.

Observed Behavior:

Given a hung rails server
When I run freethousand
Then it kills the process running my rails server
And it kills the process running all my open firefox windows

Operating System: 5.4.27-1 Manjaro
Firefox: 74 for Manjaro

At the Hashrocket Miniconf of 2018, fellow rocketeers and I proclaimed a renewed interest in the development of dotmatrix. Right now, we feel we have neglected this project simply because 'it just works'. Starting in 2018, we are actively looking to refactor parts of dotmatrix: removing anything deprecated or no longer in use and adding more relevant tooling.

With that being said, we are interested in input from the community and original contributors that helped build this tool. Please feel free to drop a comment on what you would like to see in 'dotmatrix2018'.

Thanks!

This caused me pain. Don't know of exact fix. I had to workaround this with:

sh -c './bin/install ; true'

Which basically says, this command was successful no matter what (BAD BAD BAD).

Case was for a Vagrant provisioning line. Vagrant provisioning fails if it ever encounters a non-zero return.

I'm using a fork of dotmatrix to manage my own dot files and I don't seem to have the hr command in my path. If I go to my fork and run bin/install I get hr: no such command autoinstall. I've pulled the latest from the upstream and merged it into my fork but I still can't seem to get this to work, is it something I have misconfigured?

Hi all,

I love the dotmatrix and how easy it is to set up. I am curious though, right now I have everything in my own .vimrc.local but I've been thinking about splitting my files up into categories in the .vim folder, is this still possible using the dotmatrix?

Thanks!
Brandon

I find dotmatrix useful,

namely on my 2012-2015 macbook pro. (see computer specs)

However, for the year that I have been using dotmatrix my macbook gets stuck if I am using vim and scrolling to the end of a file. The amount of time being stuck is worse if I hugely overshoot the length of the file.

Having a fresh operating system I was able to replicate the issue and can easily replicate the issue again.

Problem

the problem lies in line 11 of .vimrc

set visualbell

my understanding is that the visual bell is stopped

but awaits further instructions.

Solution

I found the solution to the problem and can make a pull request if there is interest.

solution: add to line 12 of .vimrc

set t_vb= #.note: this sets the effect of the vim visual bell to do nothing

I wanted to check two things with your team before opening a pull request,

1. If the current implementation had a particular use that I am unaware. (without set t_vb=)
2. New code will not cause trouble for users with different hardware and operating systems.

Computer Specs,

macOS Seirra version: 10.12.6

MacBook Pro (13-inch, Mid 2012)

Processor: 2.9 GHz Intel Core i7

Resource/Referance

solution sourced from: disable audio/visual bells in vim

Hello, on a factory restored MacBook computer ,
note: mac using default bash terminal

The problem,

The readme for dotmatrix states run:
cd dotmatrix;
bin/install;
Then
hr vimbundles;

The result, hr command not found.

The fix, (workaround for the problem)

When in dot-matrix directory,
Run the hr bin script:
./hr/bin/hr;

Now it seemed the hr command will be found in future use.

Summary, perhaps bin/install; is not performing the install for hr command.

Possible resolution,

Inside of #bin/install

Possible problem: $PWD/hr/bin/hr autoinstall

Possible resolution: ./$PWD/hr/bin/hr autoinstall
to actually run the script for autoinstall.

I'm not sure if this is something on my end or the dotmatrix end but here is what I'm experiencing:

• /usr/local/bin/brew is echo'd every time I start a new terminal session and it usually takes a while for the prompt to load.
• Whenever I try to use vinegar.vim or NERDTree I get UpdateLastColumn failed to find bufnr # in w:BufKillList I'm not really sure how to debug errors in vim but I've been searching for that function.
• I have vim like keybinds for moving between windows in tmux and they all work except for CTRL+L which is sending a strange command, I see ~@k in the lower right corner of tmux so I'll search for that.

Also, if you want separate issues for these or I'm just being stupid and these are my fault, let me know.

Thanks again,
Brandon

I've been digging through the .tmux.conf file recently. There are a couple lines designated as copy/paste interop:

# Copy/paste interop
bind C-c run "tmux show-buffer | reattach-to-user-namespace pbcopy"
bind C-v run "reattach-to-user-namespace pbpaste | tmux load-buffer - && tmux paste-buffer"

A couple things about this:

1. This is apparently binding Ctrl-c to run a command to copy to the Mac OSX system buffer. That's in conflict with the system's use of Ctrl-c, which is to send a SIGINT to the current application. Is this intended? Or should it instead use the meta key (i.e. Cmd) -- M-c? Update: I was forgetting that the <prefix> comes first, so this would be triggered with Ctrl-z Ctrl-c.
2. Versions of tmux 2.6+ shouldn't need to do the reattach-to-user-namespace thing anymore (source). I think that wrapper can be removed. Is there a need to support versions of tmux older than 2.6? If there is, we can add if-shell checks to only do the reattach for older versions so that reattach-to-user-namespace is not a dependency.
3. I tried commenting out these lines altogether to see what functionality they might be account for. I then held option while making a mouse selection, hit Cmd-c, then hit Cmd-v. It copy-pasted my selection as expected. So, are these lines even needed or is this just a vestige of terminals of yore? Update: Same mistake as above with the missing <prefix>.

Found myself banging my head against the wall because my script couldn't find bin/vimbundles, but it correctly found bin/install.

This was because bin/install is without the sh extension and bin/vimbunldes.sh has it. Not sure what this would entail (probably updating the docs and the files)

Not sure if this is a big enough deal to change (as other scripts may rely on those names)

There's currently a bundler config file in.bundle/config. @mattpolito and I believe the symlinking script in bin/file_list.sh is the issue.

Should we come up with a better way to symlink files? Is it even worth it for us to keep this bundler config if we aren't using it?

Edit: I have bundler-2.0.1 and it seems that rspec is the default test framework and coc is set to false by default.

I recently switched my zsh plugin manager to zplug which is a wonderful and fast plugin manager for zsh. It also allows pulling binaries or zsh files from other git repos and will allow us to include things like pear automatically with new installs.

This will also allow separating the hr binary to a separate repo if that's something people are still interested in.

The benefit of including a plugin manager for zsh is the ability to enhance zsh with new functionality such as autosuggestion, auto completion for different CLIs such as docker, using different prompts, themes, aliases and functions. All pulled from different locations / packages.

To see what's available check out:
https://github.com/unixorn/awesome-zsh-plugins

Why zplug:

• Can manage everything
  • Zsh plugins/UNIX commands on GitHub and Bitbucket
  • Gist files (gist.github.com)
  • Externally managed plugins e.g., oh-my-zsh and prezto plugins/themes
  • Binary artifacts on GitHub Releases
  • Local plugins
  • etc. (you can add your own sources!)
• Super-fast parallel installation/update
• Support for lazy-loading
• Branch/tag/commit support
• Post-update, post-load hooks
• Dependencies between packages
• Unlike antigen, no ZSH plugin file (*.plugin.zsh) required
• Interactive interface (fzf, peco, zaw, and so on)
• Cache mechanism for reducing the startup time

Also it will be similar enough for what we use for Vim (vim-plug) since it was inspired by vim-plug.

If there's interest I'll submit a PR on Friday.