| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Introduce a `projectile--cmake-command`, for CMake projects
parametrized on command-type, and route configure, build and test
commands for cmake projects through this.
This command ensures that presets for the given command-type is
supported by the installed version of CMake, that `json-parse-buffer`
is available, that the user has opted in to preset support through
the `projectile-enable-cmake-presets` custom, and that there is at
least one preset available for the given command type.
If all these conditions hold it parses the preset files and prompts
the user to select a preset, or to opt-out of preset configuration,
and creates a manual or preset command based on the users selection.
Else it will revert to manual configuration.
|
|
This adds project detection for unpacked Debian source packages. We detect
this by checking for the presence of a debian/control file even though
technically we should probably check for all of
debian/{rules,contro,changelog}. I found documenting this too cumbersome so
I went with just the control file.
In Debian there's two main (lightweight) ways of building packages:
dpkg-buildpackage and debuild. The latter is pretty much just a wrapper for
the former that also runs static checks across the resulting package.
Developers usually use debuild so that's what we use here. The -uc -us
options we hardcode are extremely common. They disable codesigning which
you'd usually not want to do for a simple developmnet build since it can
always be done using debsign before uploading the package.
Since tests usually run as part of the Debian package build and there isn't
a unified way to run just the tests we don't add a :test command.
Technically there's autopkgtest for running special 'as installed' tests
after the package build, but this requires setting up some virtualisation
drivers beforehand so it doesn't make much sense here either.
|
|
|
|
|
|
|
|
|
|
coloring clutter and fix #1647
|
|
Do not ask twice for the project root when calling
`projectile-run-ielm`, `projectile-run-term` or `projectile-run-vterm`
from outside a projectile folder.
These functions called `projectile-acquire-root` and then
`projectile-generate-process-name` which also called
`projectile-acquire-root`.
This commit modifies `projectile-generate-process-name` to require a
`project` parameter.
|
|
|
|
native indexing (#1461)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Currently, this requires that the user explicitly set
(setq compilation-buffer-name-function
#'projectile-compilation-buffer-name)
(setq compilation-save-buffers-predicate
#'projectile-current-project-buffer-p)
both of these degrade properly when not inside a project. Is there a
better way to enable these than telling a user that they should set the
variables?
Fixes #1517.
Co-authored-by: Bozhidar Batsov <bozhidar.batsov@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
Register mill as a project type in projectile.el and update the
changelog and doc with these changes.
|
|
|
|
|
|
- Add projectile-acquire-root, providing the
common (projectile-ensure-project (projectile-project-root)) idiom
- Add projectile-process-current-project-buffers-current: like
projectile-process-current-project-buffers, but calling ACTION without
arguments and with the buffer current
|
|
|
|
projectile.el: add new commands and defaults for cmake and make
doc/modules/ROOT/pages/projects.adoc: mention new commands
|
|
Added as first option, like in [spacemacs](https://develop.spacemacs.org/doc/DOCUMENTATION.html#searching) and [visual studio code](https://code.visualstudio.com/updates/v1_11#_text-search-improvements).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
projectile-dirconfig-comment-prefix.
Resolves bbatsov/projectile#1522
|
|
Originally reported under bug #675, native indexing for non-trivial
projects is extremely slow due to repeated invocations of
(projectile-ignored-[files|directories]) during recursion.
@shitikanth proposed a solution under #1495 in Feb 2020.
This PR incorporates @bbatsov's feedback on #1495 and may
resolve #1495 and close #675.
Thanks to @shitikanth for initial research and solution idea.
Benchmarking suggests at least a 10x improvement.
e.g.: indexing the projectile source project itself under linux:
(benchmark-run 3 (projectile-dir-files-native default-directory))
OLD: (2.109717349 25 0.5421294649999999)
NEW: (0.098484531 1 0.022120505000000013)
The effect was even more pronounced for me on Windows.
|
|
|
|
|
|
When TRAMP archives are enabled, back out of the archive before trying to find
the project root. Starting inside the archive makes opening archives quite slow.
|