| Commit message (Collapse) | Author | Files | Lines |
|
|
|
Apparently org-bullets is not supported anymore
Signed-off-by: Franck Cuny <franck@fcuny.net>
|
|
|
|
|
|
Since on macOS the filesystem is not case insensitive, it means that a
file named `projects.org` will be associated with YAML if the regexp is
only `PROJECT`. Making the regexp more strict fixes this issue.
|
|
Instead of having the active timestamp in the header, we can store it in
the drawer. There's not a lot of value for having this in the header, we
mostly care about the creation time for the agenda.
|
|
|
|
|
|
For some reasons using `defvar` for the files does not work with the
agenda.
Rewrite the org-capture templates to specify the files instead of
relying on the variable, since it's not working (at least on linux with
emacs 27.2).
Add a custom command for the agenda, to see what I care about for the
week.
|
|
- don't underline the highlighted line
- don't scale / change the font for the agenda
|
|
|
|
|
|
|
|
|
|
|
|
Let's not worry about synchronizing files between machines, since I want
to dissociate work from personal stuff.
Let's reduce the amount of files managed by org, and let's have fewer
templates too.
|
|
|
|
Let's use HTTPS instead of SSH for all my projects.
|
|
I'm going to deprecate the SSH endpoint for gitea, and use HTTPS instead
for accessing the repositories.
For this, I need to configure properly the credential part for the
different forges (github/gitea for now), and update the URL in the forge
configuration for emacs.
|
|
Use it with the forge package.
|
|
|
|
|
|
|
|
|
|
|
|
The emacs version on arch does not yet have support for native code
compilation, so I need to check that the variable exists before using
it.
|
|
|
|
|
|
Emacs 28 has support for native compilation which speeds up a number of
packages. This change set the path where we want to store the files.
|
|
We need a `provide` and we should only configure it if the binary is
present.
|
|
|
|
|
|
Don't use plain white for the background, but a very light yellow color.
|
|
Don't use the current branch when building a link to sourcegraph, as we
might be on a feature branch that is not available on the remote.
|
|
|
|
They are all handled by the repository `linux-desktop`. It's easier to
have a different repository for this bits of configs.
|
|
Since the hostname from the git remote is appended to
'sourcegraph.twitter.biz', we can get rid of the mapping and just build
the URL using `format`. This simplifies even more the solution.
|
|
The function needs to be defined before we use it in the `use-package`
for go-mode.
|
|
|
|
It's useful to show errors across a project
|
|
|
|
|
|
The mapping for git.twitter.biz was incorrect.
The package `git-link' has functions to take to format the URL for
sourcegraph, we don't need to maintain them on our end, which simplifies
a bit the code.
|
|
This article [1] shows how to use sourcegraph with the package
`git-link'. However, it requires to modify the configuration of the
repository to add a new remote named 'git-link'. This is inconvenient,
and this can be automated.
This change adds a function to automatically generate the remote URL
when the remote origin of a repo is set to twitter.biz.
We also add the configuration for our own gitea instance.
[1] https://sideshowcoder.com/2020/07/02/opening-sourcegraph-from-emacs/
|
|
This packages help interacting with various forges. We add a new entry
to the default list for our own gitea instance.
|
|
Sort branches by date.
|
|
The restic REST server is running on the nas' wireguard interface, so we
need to change the URL in our unit file.
|
|
|
|
|
|
|
|
When creating a new buffer for eshell with `fcuny/eshell-here` rename
the buffer using parts of the directory.
|
|
From https://www.masteringemacs.org/article/complete-guide-mastering-eshell
|
|
With zsh I report how long a command takes to execute when it takes more
than a few seconds, and it's pretty useful.
This article [1] shows how to do the same with eshell.
[1] https://www.birkey.co/2021-06-20-why-eshell-part-1.html
|
|
It breaks every time I update the package.
|
|
|