It's worked for me. Similarly i have Makefile anf Dockerfile which doesnot have extensions too. How to make comments doxygen readable for Makefile/Dockerfile? For shell scipts which does not recognised by doxygen bu i am using doxygen-bash.sed
Comments should reable by doxygen for Makefile amd Dockerfile.
Related
E.g. I have a file:
my-cmd
#/usr/bin/env python
print('hello')
or:
my-cmd-2
#/usr/bin/env bash
echo hello
the syntax highlighting is not working. It does work when I have files with extension however such as my-cmd.py or my-cmd-2.sh, so it seems that it is unable to recognize those file types by shebang.
Is this just a bug on both the Python and Bash plugins? Or is there some more global setting for it? Or is it just not possible in Eclipse currently?
I looked under the "Association" settings but I could only see filename based methods there.
Tested on Eclipse CDT 2022-09 with extensions PyDev 10.0.1 and Bash Editor 2.8.0.
I started learning OCaml several days ago. I installed everything and tested a small program on Atom which worked ok.
But I don't really understand how to work on VSC. I created a file 'test.ml',but how can I run it ?
Thanks in advance
Assuming VSC is Visual Studio Code (and you're on a Unix-like system):
If you want editing support such as auto-completions, you need to install OCaml Platform extension for VS Code by following installation steps outlined here. Note that the instructions indicate that you need to also have ocaml-lsp-server installed.
If you need to run test.ml as a program, you should do in the VS Code terminal:
$ ocamlc -o test test.ml # compile 'test.ml' into an executable 'test'
$ ./test # to run the program
Note that VS Code doesn't have a ready button to run an OCaml file as an executable (not yet at least).
Newcomers to OCaml are recommended to explore language either with ocaml or utop REPL.
How to get utop: Assuming you have opam installed, you should opam install utop. Aforementioned opam is a package manager for OCaml, that can also help you manage OCaml versions and is indispensable if you want to get serious about OCaml development.
Then you'll be able to launch utop in terminal, and inside utop, you can execute test.ml with
#use "test.ml"
assuming that utop was launched from the folder containing test.ml.
You should be able to do the same with ocaml REPL that is installed along with OCaml compiler, but it's much less convenient.
I've downloaded VSCode and installed a Verilog extensions.
Reading VsCode manual there should be a build in Make command.
First I created some verilog files.
Then I created a MakeFile with a compile command for the verilog command.
From the Terminal window I write:
Make
The only response I get is something similar like this "Make not recognized"
Am I missing some steps here ?
Example: https://gist.github.com/4057143
System: Kubuntu 12.04 (+ sudo apt-get install doxygen texlive-fonts-recommended)
When running Doxygen with a custom layout file (specified via CUSTOM_LAYOUT in the Doxyfile) it does not generate the modules.tex file (and consequently fails to build the LaTeX output). If I run Doxygen without the custom layout it generates the modules file which can be used if Doxygen is rerun with the custom layout... I see no errors in the Doxygen output.
How can I make Doxygen create modules.tex while using a custom layout file?
I installed perl-support.vim into ~/.vim (unzipped). When I create a new .pl file it shows me the default template, which means my installation is successful (I guess). I have already added filetype plugin on in ~/.vimrc & /etc/vimrc.
How do I enter a perl-support command?
The write up recommends typing \isu in normal mode for creating a new sub, but the moment I hit i vim changes into insert mode and nothing intended happens.
What am I doing wrong?
Make sure you've enabled ftplugins with the filetype plugin on command in .vimrc, and of course make sure that the file you're editing is recognized as a Perl file (usually, by having a known extension, but you can force the matter by issuing the command set filetype=perl. If filetype plugins aren't enabled, or if the filetype isn't recognized, then the rest of perl-support won't get loaded at all.
As recommended by hobbs, set filetype=perl works.
However, I wanted to do this everytime I open a .t test file — which my vim does not recognize as perl files because the interpreter statement is also custom.
I checked out :help syntax in vim and saw this:
mkdir ~/.vim/ftdetect
cd ~/.vim/ftdetect
vim t.vim
which contains
au BufRead,BufNewFile *.t set filetype=perl
which means: if the file extension is .t then do set filetype=perl.
This can be useful for any other custom extension.
I found I had to install Perl::Tags before most things (esp. \ commands). Installing Perl::Tags made an error message thrown by filetype plugin on go away.
cpan> install Perl::Tags # make sure you say yes to any offer to install dependancies