exec-path-from-shell
virtual-environments
exec-path-from-shell | virtual-environments | |
---|---|---|
29 | 54 | |
1,366 | 6,399 | |
- | - | |
6.0 | 9.8 | |
about 1 month ago | over 1 year ago | |
Emacs Lisp | PowerShell | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
exec-path-from-shell
-
Thinking about buying a macbook, does Emacs work well?
I'm not a Mac user, but FWIW from what I've seen over time https://github.com/purcell/exec-path-from-shell is a must when using Emacs on a Mac. I don't know why this is, but I'm guessing there's something unusually difficult about setting up the desktop session environment when using OSX, and users end up needing to resort to this. Hopefully that helps if you run into environment issues.
- LSP-Mode doesn't find pylsp even though it's in PATH
- First Time Emacs User on macOS - Need Guidance!
-
WSL issue
Check out the package exec-path-from-shell
-
Magit - SSH-agent
This package may help: https://github.com/purcell/exec-path-from-shell
- Why does emacs exec path variable not just copy the users path variable?
-
Eshell cannot find executable even directory is specified in the $PATH
All my path related problems with emacs were solved with the package: https://github.com/purcell/exec-path-from-shell
-
Minor problems with vterm in emacs on MacOS
For one, do you use the exec-path-from-shell package? That should do the trick for path issues when using Emacs vterm. It's likely when emacs is loading it's not correctly loading in the $PATH values from your system. You can check the path values in emacs by checking the value of exec-path.
-
Help with projectile default action
I would like to use SPC p p RET to switch projects, change working directories to trigger exec-path-from-shell, and open Treemacs with the only active project being the selected one.
-
Issues building Emacs.app for Mac OS from source with native compilation
I suspect the Emacs.app package has some misconfigured paths that are unable to find my libgccjit library, which I've installed via homebrew. I've tried experimenting with exec-path-from-shell to ensure Emacs is aware of my shell paths, but to no avail.
virtual-environments
-
Deploy to Google AppEngine with GitHubActions
This action runs using Node 16. If you are using self-hosted GitHub Actions runners, you must use runner version 2.285.0 or newer.
-
Ensuring Your E2E Tests Run On Every Code Push
This is the OS and version used for the virtual environment in which run our tests. I recommend always using a specific version, such as the latest stable version, rather than latest, which is risky because you may then suddenly start to see test failures caused by a version update that has nothing to do with your tests. See virtual-enviroments for the latest stable version.
-
How would you suggest running unit tests within containers in a CI AKS based considering docker.sock isnβt available anymore?
This, I setup Azure DevOps pipeline that clones this: https://github.com/actions/virtual-environments Runs it in Linux servers, copies VHD into Storage Account, creates an image from it and makes it new image for Azure Scale Set. Runs every Monday Morning on timer.
-
Ask HN: How are you dealing with the M1/ARM migration?
I'm in a similar boat - love the performance/battery of my M1 MacBook Air, but the ecosystem is just too messy at the moment for me. I have a few tools I need to use that haven't yet been making official Apple Silicon releases due to GitHub actions not supporting Apple Silicon fully yet. The workaround involves maintaining two versions of homebrew, one for ARM and one for x86-64, and then being super careful to make sure you don't forget if you're working in an environment that's ARM and one that's X86. It's too much of a pain to keep straight for me (I admit it - I lack patience and am forgetful, so this is a bit of a "me" problem versus a tech problem).
My solution was to give up using my M1 mac for development work. It sits on a desk as my email and music machine, and I moved all my dev work to an x86 Linux laptop. I'll probably drift back to my mac if the tools I need start to properly support Apple Silicon without hacky workarounds, but until GitHub actions supports it and people start doing official releases through that mechanism, I'm kinda stuck.
It is interesting how much impact GitHub has had by not having Apple Silicon support. Just look at the ticket for this issue to see the surprisingly long list of projects that are affected. (See: https://github.com/actions/virtual-environments/issues/2187)
-
Struggling to setup GithubAction with a .NET 4 app build
https://github.com/actions/virtual-environments/issues you can always request additional software to added to GitHub's machines, costs nothing to ask.
-
Any tool that can help me convert Azure ADO Pipelines to GitHub Actions YAML?
I'm not disputing your claim that it could be true as I say, it makes sense, there is even some evidence they are getting ready for feature parity as I said in my comment with the hosted agent builds but I am arguing the point with my "what aboutism" as it isn't clear.
-
Czkawka 4.1.0 - Fast duplicate finder, with finding invalid extensions, faster previews, builtin icons and a lot of fixes
Also Ubuntu 22.04 is not currently available on Github so I can't use CI for now - https://github.com/actions/virtual-environments/issues/5428
-
Emacs 28.1's been cut
As for M1 support, Iβm still waiting for GitHub to add M1-based GitHub Actions runners (issue).
-
Getting started with GitHub Actions and workflows
GitHub provides hosted runners which can run your workflow in different virtual environments. The "ubuntu-latest" environment already contains a recent version of Node.js which is ideal for testing JavaScript applications.
-
AzurePipeline failing due to: The reference assemblies for .NETFramework,Version=v4.6.1 were not found
As mentioned in this GitHub issue, the issue seems to affect only windows-2022 image. You can use the following script to install .NETFramework 4.6.1 to the agent.
What are some alternatives?
build-emacs-for-macos - Somewhat hacky script to automate building of Emac.app on macOS.
action-gh-release - π¦ :octocat: GitHub Action for creating GitHub Releases
neovim-ide - NeoVim as IDE
act - Run your GitHub Actions locally π
SLANOMACS - My (Illiterate) Literate Doom Emacs Config
widevine-l3-guesser
build-emacs-macos - Build script for emacs and macos
runner - The Runner for GitHub Actions :rocket:
emacs-jupyter - emacs plug-in to run python code inside tex or markdown buffer
SwagLyrics-For-Spotify - π Get lyrics of currently playing Spotify song so you don't sing along with the wrong ones and embarrass yourself later. Very fast.
jupyter - An interface to communicate with Jupyter kernels.
UTM - Virtual machines for iOS and macOS