Code Monkey home page Code Monkey logo

laptop's People

Contributors

22antonio avatar dropsofserenity avatar karvel avatar michaelachrisco avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

laptop's Issues

Add Arch Compatibility

Desired Use Case

The dotfiles should support Arch and Arch-based systems.

Actual/Current Behavior

Not yet implemented.

Steps to Implement This Feature

  1. Find way to determine that the OS is Arch or Arch-derived.
  2. Install the same suite of packages via pacman.

Learning

The unauthenticated git protocol on port 9418 is no longer supported.

Describe the bug
Received an error while installing
Cloning into '/Users/kenclements/.zsh/completion'...
fatal: remote error:
The unauthenticated git protocol on port 9418 is no longer supported.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.

To Reproduce
Steps to reproduce the behavior:

  1. Run ./setup

Expected behavior
Shift3 will install required software

Screenshots
Homebrew Bundle complete! 23 Brewfile dependencies now installed.

Already using zsh ...
Cloning into '/Users/kenclements/.zsh/completion'...
fatal: remote error:
The unauthenticated git protocol on port 9418 is no longer supported.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.

Desktop (please complete the following information):

  • OS: macOS Monterey 12.3 (21E230)

Additional resources
Did a google search and found this link:
here
https://stackoverflow.com/questions/70663523/the-unauthenticated-git-protocol-on-port-9418-is-no-longer-supported

We took the following steps:
Used rscherer solution found roughly in the middle of the page.

(M1 Mac) After setup of laptop script, brew not recognized as a zsh command

On an M1 Mac running Monterey, after running the laptop setup, brew is not quite recognized as a zsh command.

staging (main) # brew -v
zsh: command not found: brew

I was able to solve this by adding the following line to ~/.zshrc:

# for mac systems this will pickup homebrew, otherwise nice to have.
export PATH="/usr/local/bin:$PATH"
export PATH="/opt/homebrew/bin:$PATH" # the fix

zsh compinit: insecure directories

I got the following warning on a new Macbook Pro 2019:
Mac OS Version: 10.15.4

New setup without any customization.

Last login: Tue Apr  7 09:29:14 on ttys000
zsh compinit: insecure directories, run compaudit for list.
Ignore insecure directories and continue [y] or abort compinit [n]? y
zsh compinit: insecure directories, run compaudit for list.
Ignore insecure directories and continue [y] or abort compinit [n]? compinit: initialization aborted
complete:13: command not found: compdef
~ # compaudit
There are insecure directories:
/usr/local/share/zsh/site-functions
/usr/local/share/zsh

Long term maintanance of the repo

@coreyshuman / @mwallert / Anyone
Couple of questions that are related to this repo.

What does long term maintenance look like for this repo? Justin spearheaded this repo (and did an amazing job at it) but now we dont have a dedicated dev/team looking at our common tools (at least that I am aware).

Does the shop still use this in the on-boarding of new developers?

Should DevOps own this repo or Architecture? Someone else?

I personally still think it still provides value. And I would still like to se tfswitch to be part of the repo as well as more testing within the Mac OS side (Circleci or otherwise). But I would like to hear peoples thoughts and get their feedback. I have a feeling most just set and forget about these tools once the are installed.

Edit Readme

  • Edit readme for clarity.
  • Provide link to equivalent Windows guide.
  • Add explanation for acronym (TLS).

Destroys Previous ZSH Configuration

I was running the PowerLevel10k ZSH theme and it got unset by the script.
Everything seems to still be there, I'm guessing it just got moved over to the default or other custom theme.

Bug: set nocompatible on first line is ignored

Desired Use Case
Allow the use of arrow keys in vim.

Actual/Current Behavior
Currently the arrow keys don't work. The solution is to add set nocompatible. This option is already set in the first line. However, for some reason that I have not found it is ignored.

Steps to Implement This Feature
Move set nocompatible lower in the file. It's no longer ignored lower in the file.

Learning

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.