libguestfs/libguestfs-docs-master — French @ Fedora Weblate: ;;; In libguestfs, indent with spaces everywhere (not TABs). ;;; …

Zen

Translation

English type: verbatim

;;; In libguestfs, indent with spaces everywhere (not TABs).
;;; Exceptions: Makefile and ChangeLog modes.
(add-hook 'find-file-hook
'(lambda () (if (and buffer-file-name
(string-match "/libguestfs\\>"
(buffer-file-name))
(not (string-equal mode-name "Change Log"))
(not (string-equal mode-name "Makefile")))
(setq indent-tabs-mode nil))))

French

;;; In libguestfs, indent with spaces everywhere (not TABs). ;;; Exceptions: Makefile and ChangeLog modes. (add-hook 'find-file-hook '(lambda () (if (and buffer-file-name (string-match "/libguestfs\\>" (buffer-file-name)) (not (string-equal mode-name "Change Log")) (not (string-equal mode-name "Makefile"))) (setq indent-tabs-mode nil))))

Needs editing

Skip

	English	French	Actions
	Adding tests for language bindings
	Language bindings should come with tests. Previously testing of language bindings was rather ad-hoc, but we have been trying to formalize the set of tests that every language binding should use.
	Currently only the OCaml and Perl bindings actually implement the full set of tests, and the OCaml bindings are canonical, so you should emulate what the OCaml tests do.
	This is the numbering scheme used by the tests:
	- 000+ basic tests:	- 000+ basic tests:
	010 load the library 020 create 030 create-flags 040 create multiple handles 050 test setting and getting config properties 060 explicit close 065 implicit close (in GC'd languages) 070 optargs 080 version 090 retvalues
	- 100 launch, create partitions and LVs and filesystems	- 100 launch, create partitions and LVs and filesystems
	- 400+ events:	- 400+ events:
	410 close event 420 log messages 430 progress messages	410 close event 420 log messages 430 progress messages
	- 800+ regression tests (specific to the language)	- 800+ regression tests (specific to the language)
	- 900+ any other custom tests for the language	- 900+ any other custom tests for the language
	To save time when running the tests, only 100, 430, 800+, 900+ should launch the handle.
	FORMATTING CODE
	Our C source code generally adheres to some basic code-formatting conventions. The existing code base is not totally consistent on this front, but we do prefer that contributed code be formatted similarly. In short, use spaces-not-TABs for indentation, use 2 spaces for each indentation level, and other than that, follow the K&R style.
	If you use Emacs, add the following to one of your start-up files (e.g., ~/.emacs), to help ensure that you get indentation right:
	;;; In libguestfs, indent with spaces everywhere (not TABs). ;;; Exceptions: Makefile and ChangeLog modes. (add-hook 'find-file-hook '(lambda () (if (and buffer-file-name (string-match "/libguestfs\\>" (buffer-file-name)) (not (string-equal mode-name "Change Log")) (not (string-equal mode-name "Makefile"))) (setq indent-tabs-mode nil))))	;;; In libguestfs, indent with spaces everywhere (not TABs). ;;; Exceptions: Makefile and ChangeLog modes. (add-hook 'find-file-hook '(lambda () (if (and buffer-file-name (string-match "/libguestfs\\>" (buffer-file-name)) (not (string-equal mode-name "Change Log")) (not (string-equal mode-name "Makefile"))) (setq indent-tabs-mode nil))))
	;;; When editing C sources in libguestfs, use this style. (defun libguestfs-c-mode () "C mode with adjusted defaults for use with libguestfs." (interactive) (c-set-style "K&R") (setq c-indent-level 2) (setq c-basic-offset 2)) (add-hook 'c-mode-hook '(lambda () (if (string-match "/libguestfs\\>" (buffer-file-name)) (libguestfs-c-mode))))	;;; When editing C sources in libguestfs, use this style. (defun libguestfs-c-mode () "C mode with adjusted defaults for use with libguestfs." (interactive) (c-set-style "K&R") (setq c-indent-level 2) (setq c-basic-offset 2)) (add-hook 'c-mode-hook '(lambda () (if (string-match "/libguestfs\\>" (buffer-file-name)) (libguestfs-c-mode))))
	TESTING YOUR CHANGES
	Turn warnings into errors when developing to make warnings hard to ignore:
	./configure --enable-werror
	Useful targets are:
	C<make check>	C<make check>
	Runs the regular test suite.
	This is implemented using the regular automake C<TESTS> target. See the automake documentation for details.
	C<make check-valgrind>	C<make check-valgrind>
	Runs a subset of the test suite under valgrind.
	See L</VALGRIND> below.
	C<make check-valgrind-local-guests>	C<make check-valgrind-local-guests>
	Runs a subset of the test suite under valgrind using locally installed libvirt guests (read-only).
	C<make check-direct>	C<make check-direct>
	Runs all tests using default appliance back-end. This only has any effect if a non-default backend was selected using C<./configure --with-default-backend=...>

Loading…

No matching activity found.

Browse all string changes

Things to check

Punctuation spacing `1`

Missing non breakable space before double punctuation sign

Fix string

Reset

Unchanged translation `2`

Source and translation are identical

Reset

Glossary

English	French
No related strings found in the glossary.

5324301 String information

Source string description

type: verbatim

Flags

no-wrap

Source string location

../docs/guestfs-hacking.pod:595

String age

4 years ago

Last updated

a year ago

Source string age