Search
1000 results for “davemq”
-
I installed "b4" using "pipx", which sets up a virtual environment for the "b4" code and its dependencies. I looked for a way to set TMPDIR to the current working directory when running "b4".
After some research, I found I could create a "foo.pth" file in the pipx virtual environment's site-pakages directory, which a 1 liner:
import os; os.environ['TMPDIR'] = os.getenv('PWD')
This did the trick! b4 prep --edit-cover now works with emacsclient and Magit!
5/5
-
I installed "b4" using "pipx", which sets up a virtual environment for the "b4" code and its dependencies. I looked for a way to set TMPDIR to the current working directory when running "b4".
After some research, I found I could create a "foo.pth" file in the pipx virtual environment's site-pakages directory, which a 1 liner:
import os; os.environ['TMPDIR'] = os.getenv('PWD')
This did the trick! b4 prep --edit-cover now works with emacsclient and Magit!
5/5
-
I installed "b4" using "pipx", which sets up a virtual environment for the "b4" code and its dependencies. I looked for a way to set TMPDIR to the current working directory when running "b4".
After some research, I found I could create a "foo.pth" file in the pipx virtual environment's site-pakages directory, which a 1 liner:
import os; os.environ['TMPDIR'] = os.getenv('PWD')
This did the trick! b4 prep --edit-cover now works with emacsclient and Magit!
5/5
-
I installed "b4" using "pipx", which sets up a virtual environment for the "b4" code and its dependencies. I looked for a way to set TMPDIR to the current working directory when running "b4".
After some research, I found I could create a "foo.pth" file in the pipx virtual environment's site-pakages directory, which a 1 liner:
import os; os.environ['TMPDIR'] = os.getenv('PWD')
This did the trick! b4 prep --edit-cover now works with emacsclient and Magit!
5/5
-
I installed "b4" using "pipx", which sets up a virtual environment for the "b4" code and its dependencies. I looked for a way to set TMPDIR to the current working directory when running "b4".
After some research, I found I could create a "foo.pth" file in the pipx virtual environment's site-pakages directory, which a 1 liner:
import os; os.environ['TMPDIR'] = os.getenv('PWD')
This did the trick! b4 prep --edit-cover now works with emacsclient and Magit!
5/5
-
I'm not sure why Magit really cares. I tried using advice to get around this, but didn't quite get it to work.
Looking at the "b4", I found the Python code for editing the cover letter. It creates a temporary directory and then "COMMIT_EDITMSG" in that directory. Looking at the documentation for tempfile.TemporaryDirectory suggested using an environment variable like TMPDIR. Okay, this is another idea, set TMPDIR to the current working directory.
4/5
-
I'm not sure why Magit really cares. I tried using advice to get around this, but didn't quite get it to work.
Looking at the "b4", I found the Python code for editing the cover letter. It creates a temporary directory and then "COMMIT_EDITMSG" in that directory. Looking at the documentation for tempfile.TemporaryDirectory suggested using an environment variable like TMPDIR. Okay, this is another idea, set TMPDIR to the current working directory.
4/5
-
I'm not sure why Magit really cares. I tried using advice to get around this, but didn't quite get it to work.
Looking at the "b4", I found the Python code for editing the cover letter. It creates a temporary directory and then "COMMIT_EDITMSG" in that directory. Looking at the documentation for tempfile.TemporaryDirectory suggested using an environment variable like TMPDIR. Okay, this is another idea, set TMPDIR to the current working directory.
4/5
-
I'm not sure why Magit really cares. I tried using advice to get around this, but didn't quite get it to work.
Looking at the "b4", I found the Python code for editing the cover letter. It creates a temporary directory and then "COMMIT_EDITMSG" in that directory. Looking at the documentation for tempfile.TemporaryDirectory suggested using an environment variable like TMPDIR. Okay, this is another idea, set TMPDIR to the current working directory.
4/5
-
I'm not sure why Magit really cares. I tried using advice to get around this, but didn't quite get it to work.
Looking at the "b4", I found the Python code for editing the cover letter. It creates a temporary directory and then "COMMIT_EDITMSG" in that directory. Looking at the documentation for tempfile.TemporaryDirectory suggested using an environment variable like TMPDIR. Okay, this is another idea, set TMPDIR to the current working directory.
4/5
-
The file is showing in Emacs. I tried to exit the emacsclient session with C-x #, and it asked if I wanted to create the directory where the file lived. Sure, I say. But at this point its useless. So I looked for ways to work around or fix this problem. With Emacs, I suspect Magit was involved. Looking at the source code, I found the places where this error was triggered. There was no easy way to get around this, other than put the file in the repository directory tree.
3/5
-
The file is showing in Emacs. I tried to exit the emacsclient session with C-x #, and it asked if I wanted to create the directory where the file lived. Sure, I say. But at this point its useless. So I looked for ways to work around or fix this problem. With Emacs, I suspect Magit was involved. Looking at the source code, I found the places where this error was triggered. There was no easy way to get around this, other than put the file in the repository directory tree.
3/5
-
The file is showing in Emacs. I tried to exit the emacsclient session with C-x #, and it asked if I wanted to create the directory where the file lived. Sure, I say. But at this point its useless. So I looked for ways to work around or fix this problem. With Emacs, I suspect Magit was involved. Looking at the source code, I found the places where this error was triggered. There was no easy way to get around this, other than put the file in the repository directory tree.
3/5
-
The file is showing in Emacs. I tried to exit the emacsclient session with C-x #, and it asked if I wanted to create the directory where the file lived. Sure, I say. But at this point its useless. So I looked for ways to work around or fix this problem. With Emacs, I suspect Magit was involved. Looking at the source code, I found the places where this error was triggered. There was no easy way to get around this, other than put the file in the repository directory tree.
3/5
-
The file is showing in Emacs. I tried to exit the emacsclient session with C-x #, and it asked if I wanted to create the directory where the file lived. Sure, I say. But at this point its useless. So I looked for ways to work around or fix this problem. With Emacs, I suspect Magit was involved. Looking at the source code, I found the places where this error was triggered. There was no easy way to get around this, other than put the file in the repository directory tree.
3/5
-
"b4 prep --edit-cover" uses the EDITOR environment variable to figure out which editor to use. Apparently the default for bash on Fedora 42 is to set EDITOR to /usr/bin/vim. While I'm quite versed in vi (the predecessor to vim), I prefer to use Emacs. So I set EDITOR to emacsclient and tried again. But this time I got an error about the file not being in a Git repository, and b4 said the file hadn't changed.
2/5
-
I recently found a small typo in some Linux kernel documentation, and posted a patch to get it fixed. There were some problems with the patch, and it was suggested I use a tool called "b4" https://b4.docs.kernel.org/en/latest/index.html. I started using it for my next patch revision, but ran into a snag when editing the patch cover file.
1/5
-
Fortunately, the wrist heart rate monitor coming back to life saved me a bunch of money, as I'm no longer conisdering purchasing a newer #Garmin #fenix7xpro at this time!
-
Fortunately, the wrist heart rate monitor coming back to life saved me a bunch of money, as I'm no longer conisdering purchasing a newer #Garmin #fenix7xpro at this time!
-
Fortunately, the wrist heart rate monitor coming back to life saved me a bunch of money, as I'm no longer conisdering purchasing a newer #Garmin #fenix7xpro at this time!
-
Fortunately, the wrist heart rate monitor coming back to life saved me a bunch of money, as I'm no longer conisdering purchasing a newer #Garmin #fenix7xpro at this time!
-
Fortunately, the wrist heart rate monitor coming back to life saved me a bunch of money, as I'm no longer conisdering purchasing a newer #Garmin #fenix7xpro at this time!
-
@HippieScubaSteve Someone who studies computer programming languages might have written that as EBNF instead #ebnf
-
I'm thinking of renaming our youngest cat Ivan so I can say "Ivan, you idiot!" when he does idiotic things #vorkosigan