| Commit message (Collapse) | Author | Files | Lines |
|
|
|
Adding a menu for hydra, to jump quickly to some files.
I'm also adding a few custom commands for the agenda. After that many
experiment, I think this is what I'm missing to be more
efficient. This allows me to ignore completely how the file *looks*
and focus on getting through the tasks.
I'm also adding a few keywords for managing tasks:
- PROJECT is for large tasks (e.g. an epic). This can be transitioned
to PROJECTDONE
- MEETING and NOTES are tasks that are completed, and I use them to
keep track of various things in a project.
|
|
I'm using 3 columns, this seems to do nothing, and not annoyed enough
to go read the doc.
|
|
|
|
|
|
Use emacs implementation of `ls`, which allows us to group files by
type (only GNU's `ls` does that, not the one shipped by MacOS)
|
|
The list of tools to install is move to an org file where I can
execute the block to install everything.
Remove extra new lines that make the file harder to read.
|
|
open a magit-status buffer when running `gs`.
|
|
especially nice for switching buffer with the minibuffer view, it
shows a little bit more information.
|
|
this modeline is nice and easy to spot which modes are enabled.
|
|
this is useful to format a json buffer using jq.
|
|
|
|
this is super annoying, it tries to complete strings in comments,
which is not what i need, i only care about completion for the code.
|
|
|
|
|
|
|
|
|
|
|
|
set the correct title of the file for org journal, and don't add the
current file when creating a new entry with org-capture.
|
|
* `fcuny/gocs` is to use twitter's internal code search engine.
* `fcuny/uniqify-region-lines` is to remove duplicated lines (useful
when lines are sorted)
* `fcuny/org-journal-date-format-func` is to set the correct title of
the journal file
|
|
add a few more bindings to the menu, mostly for navigation and tests.
|
|
|
|
one template is enough to capture what ever is going on. too much
choices makes it less likely i'll use it.
|
|
|
|
there's no `json-mode`, only `js-mode`.
|
|
|
|
i've used the workflow documented at
http://www.howardism.org/Technical/Emacs/getting-more-boxes-done.html
for the last few days and it's definitely better than anything i've
tried so far.
the rewrite is mostly to replicate the configuration (with some minor
adjustments).
|
|
|
|
small change to the capture template
|
|
this is pretty ugly and not really helpful.
|
|
|
|
add a few more variables for that module
|
|
review the grouping order (org first, for example, and group a few
more file extensions together).
|
|
guide key was not that helpful, hydra is a better way to deal with
that problem.
update ibuffer config to group files by major mode.
|
|
add configuration for ediff, and update the settings for the paren
mode.
|
|
with trailing white space highlight on by default, they are
highlighted in places i don't care (e.g. mini buffer) and this is
distracting. instead, only enable them for the modes i really care
about.
|
|
|
|
|
|
|
|
move the requirement for `company-go` to the module for go.
rework the configuration for hydra, to make it a little bit easier.
force length of comments to 80 characters per line.
|
|
improve the support to write go code. adding hydra to don't have to
remember all the commands i want to use with `go-guru`, and add
`gotest` to run tests directly from emacs.
add `company-go` for code completion.
will likely add more commands to hydra as i go.
|
|
drop some old alias for url
|
|
|
|
mostly inspired by reading https://github.com/patrickt/emacs. i've
made the configuration of counsel and ivy more explicit, by splitting
the customization.
i've fixed the binding for searching with a buffer to rely on rgrep
instead of ag (since i've switched to rg).
i'm going to try the module 'guide-key' to see if i can be better at
remembering some bindings (i always forget a bunch of them).
|
|
|
|
I switched to macport, and I don't have GNU ls anymore.
|
|
|
|
|
|
There's a bunch of binaries that are completely out dated, and this is
causing a lot of stuff to fail with emacs.
|
|
|
|
They are not easy to read, and it's easier to go to the message buffer
when debugging something.
|
|
In the next version of OS X, zsh will become the default shell.
|
|
|
|
|
|
|