| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Debug Adapter Protocol (DAP) is wire protocol to communicate between a
client and debug server. This is similar to LSP, but for debuggers.
This initial configuration focuses on enabling the mode and setting the
layout for the various buffers (in this case I want the different
buffers on the right screen and keep the main part focused on the code).
I also disable some widget to use the debugger with hydra.
There's still a number of things that are incomplete when it comes to
integrate DAP and delve (the go debugger): there's no way to call
functions, to have access to the variables, etc. But this is a good
start though, to debug simple problems without relying on print
statement.
This also update the configuration for =go= so that =M-x compile=, when
editing a go file, by default will use =go build=. This is not what I
always need / want but this is a good default.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
I need the highlighted line to be intense, with high contrast (other I'm
unable to find it the buffers). I accidently selected
'underline-only-accented' instead of 'intense-background'. This change
restore the proper value.
|
| |
|
|
|
| |
Stop using a special character for the ellipsis, and use the standard
org-bullets configuration.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
I want the title for org sections to have different size and also to
have different colors. This is done by setting the
`modus-themes-scale-headings` variable to true, and configuring the
various `modus-themes-scale-*` variables. The coloring is controlled
with `modus-themes-headings`.
Make the highlight line a bit more intense so that it's easier to spot
on the screen.
|
| |
|
|
|
|
|
|
|
| |
The module `magit-repos' can list the status of git repositories under a
given path.
Since all my repositories are under `~/workspace`, it's easy to use `M-x
magit-list-repositories` to get a buffer with all my repositories, and
their status (are they dirty, etc).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
Start using `doct` to manage the configuration for capturing content.
Try to simplify a bit.
|
| | |
|
| |
|
|
|
|
| |
When working with 'source', magit is extremely slow (source is a huge
repository, so it's not surprising). We can improve significantly
performances by disabling a number of hooks when running git status.
|
| | |
|
| |
|
