Skip to main content

Questions tagged [make]

0 votes
1 answer
46 views

I don't understand how to make $* to work when I set &makeprg. For example, if I set &makeprg = 'pandoc --from=markdown --output %:p:r:S.$* -- %:p:S' and I run make html, then the $* is not ...
Barzi2001's user avatar
  • 1,133
4 votes
1 answer
352 views

I've just encountered a new undesired behavior in Vim, possibly related to the :make command: I have a makefile with a check target that runs a Gtk4 GUI app that I'm working on. When I dismiss the app ...
RadlyEel's user avatar
  • 183
1 vote
1 answer
1k views

My question could fairly be a duplicate of this, but I hope I'm making it critically different by asking about :makeing Vim itself and having a meaningful quickfix window. (In reality, my use case is ...
Enlico's user avatar
  • 2,330
2 votes
3 answers
175 views

If I make a mistake in a class in some C++ code, I'll typically get a ton of messages from the compiler about how hard it's tried to find something suitable in system header files. This floods the ...
sh1's user avatar
  • 143
3 votes
3 answers
543 views

In general, I have makefiles setup anytime I'm working on C projects. To save and compile these projects, I've bound the ' key to do this: map ' :wa<CR>:!make<CR> However, I sometimes ...
user45331's user avatar
1 vote
0 answers
107 views

When I run a command using make, it runs from a different directory than running it as a regular command with !. My app is a CBRA, and I open vim from within a component. The top-level app, though, is ...
BassguitarBill's user avatar
4 votes
1 answer
170 views

When I use :make, the command first shows me the shell and has me press Enter and only then do I get to the actual error in the file. Is there a reason for this behaviour ? Can I get rid of it ?
cassepipe's user avatar
  • 537
1 vote
0 answers
46 views

I have a project where make and vim are run from different directories. The project structure looks like this: root/ ├── build │   └── gmake_linux │   ├── bin │   │   └── Debug │   ...
aghast's user avatar
  • 239
0 votes
1 answer
601 views

Currently, I have begun using vim for C++ projects. I use vimspector for debugging help. This offers a command :call vimspector#Launch() to debug the current successful build. To build the current ...
Tryer's user avatar
  • 247
1 vote
1 answer
94 views

I have the following .vimrc: let &makeprg="./run-tests" The contents of run-tests: #!/bin/sh error_file=$(mktemp) coverage run --source "$PWD" --branch -m pytest tests/ >&...
Edward Chamberlain's user avatar
1 vote
2 answers
617 views

Let's say I have the following script: sudo apt update sudo apt upgrade sudo apt install jq sudo apt install jo If I use the command :set makeprg=bash\ % | make inside Vim, the system will ask me my ...
raylight's user avatar
  • 605
1 vote
1 answer
263 views

Let's say that I have the following node.js script: console.log("test") If I use the command :set makeprg=node\ % | set autowrite | make I'll execute this node.js code and see the following ...
raylight's user avatar
  • 605
1 vote
2 answers
294 views

Whenever I run :make in Vim, it always takes control away from my buffer, places me in a temporary view where I see the makeprg's output and then prompts me to "Press ENTER or type command to ...
ColinKennedy's user avatar