Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] abuild.in: add default bashcomp zshcomp and fishcomp functions #74

Closed
wants to merge 1 commit into from
Closed

Conversation

maxice8
Copy link
Contributor

@maxice8 maxice8 commented May 2, 2019

No description provided.

abuild.in Outdated

cd "$pkgdir" || return 0
for i in $(find usr/share/bash-completion/completions etc/bash_completion.d -type f 2>/dev/null); do
install -Dm0644 "$i" "$subpkgdir"/usr/share/bash-completion/completions/"$(basename $i)"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Subpackage functions usually use mkdir + mv, like this you end up with a copy in the main package and in the completion package.
This applies to all 3 functions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

abuild.in Outdated Show resolved Hide resolved
abuild.in Outdated

cd "$pkgdir" || return 0
for i in $(find usr/share/bash-completion/completions etc/bash_completion.d -type f 2>/dev/null); do
mkdir -p "$subpkgdir"/"${1%/*}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think these functions have positional args, do you perhaps mean:

Suggested change
mkdir -p "$subpkgdir"/"${1%/*}"
mkdir -p "$subpkgdir"/"${i%/*}"

@maxice8
Copy link
Contributor Author

maxice8 commented May 2, 2019 via email

@maxice8
Copy link
Contributor Author

maxice8 commented May 2, 2019 via email

@maxice8
Copy link
Contributor Author

maxice8 commented May 7, 2019

@5paceToast please check again i decided to use mkdir + mv + rm

@CosmicToast
Copy link
Contributor

I think this should wait for the amove patches and use those.
amove patches are waiting for 3.10's release.
I'll try and remember to link this when opening.

@maxice8
Copy link
Contributor Author

maxice8 commented May 7, 2019

Ok i'll put this as WIP

@maxice8 maxice8 changed the title abuild.in: add default bashcomp zshcomp and fishcomp functions [WIP] abuild.in: add default bashcomp zshcomp and fishcomp functions May 7, 2019
@CosmicToast CosmicToast mentioned this pull request Jun 19, 2019
@maxice8
Copy link
Contributor Author

maxice8 commented Jan 12, 2020

amove() is in, i'll update add this to gitlab

@algitbot
Copy link

Merged in d582696 by @ncopa. Thanks for your contribution!

(This pull request has been closed automatically by GitHub PR Closer. If you think that it’s not resolved yet, please add a comment.)

@algitbot algitbot closed this Jan 28, 2020
@ichit
Copy link

ichit commented Jan 30, 2020

docker cant does not run: please can somebody help me on how to make docker run on my system. After carefully following the instruction on installing docker on alpine page and installed it on my system, each time i start docker i see the following error: Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is th?
errors pretty printing info. i have restart docker but no solution. i really need docker operating in my system. please help

1 similar comment
@ichit
Copy link

ichit commented Jan 30, 2020

docker cant does not run: please can somebody help me on how to make docker run on my system. After carefully following the instruction on installing docker on alpine page and installed it on my system, each time i start docker i see the following error: Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is th?
errors pretty printing info. i have restart docker but no solution. i really need docker operating in my system. please help

@mor1
Copy link
Contributor

mor1 commented Jan 30, 2020

@ichit This isn't really the place for reports on Docker not running -- you'd be best to go through Docker support channels (their Github etc).

However, by the sounds of it you may need to add your user account to the docker group so that you can run docker without using sudo. (That error suggests that when you run the docker command line tool, it's unable to open the UNIX socket that it uses to communicate with the actual Docker daemon; checking ls -l /var/run/docker.sock and the output of id would confirm this.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants