mirror of
https://gitlab.gnome.org/GNOME/gimp.git
synced 2025-07-03 09:23:24 +00:00
Fix spelling errors found with codespell
This commit is contained in:
Daniele Forsi
Alx Sa
parent
1a1c52d0ba
commit
994137a82e
42 changed files with 55 additions and 55 deletions
|
|
@ -6,7 +6,7 @@ There are some basic steps to building and installing GIMP.
|
|||
|
||||
GIMP @GIMP_APP_VERSION@ replaces earlier GIMP 2.10.x versions. It is advised to
|
||||
uninstall them before installing GIMP @GIMP_APP_VERSION@. Since libgimp* libraries
|
||||
and data are all versionned anyway, it is possible to keep your older
|
||||
and data are all versioned anyway, it is possible to keep your older
|
||||
GIMP 2.x installation in parallel to GIMP @GIMP_APP_VERSION@ on a same prefix.
|
||||
|
||||
GIMP @GIMP_APP_VERSION@ is not backward compatible with GIMP 2.10 and earlier
|
||||
|
|
|
|||
|
|
@ -246,7 +246,7 @@ gimp_gui_config_class_init (GimpGuiConfigClass *klass)
|
|||
|
||||
GIMP_CONFIG_PROP_BOOLEAN (object_class, PROP_RESTORE_ACCELS,
|
||||
"restore-accels",
|
||||
"Restore acclerator",
|
||||
"Restore accelerator",
|
||||
RESTORE_ACCELS_BLURB,
|
||||
TRUE,
|
||||
GIMP_PARAM_STATIC_STRINGS);
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@ gimp_operation_border_class_init (GimpOperationBorderClass *klass)
|
|||
g_object_class_install_property (object_class, PROP_RADIUS_X,
|
||||
g_param_spec_int ("radius-x",
|
||||
"Radius X",
|
||||
"Border radius in X diection",
|
||||
"Border radius in X direction",
|
||||
1, 2342, 1,
|
||||
G_PARAM_READWRITE |
|
||||
G_PARAM_CONSTRUCT));
|
||||
|
|
@ -106,7 +106,7 @@ gimp_operation_border_class_init (GimpOperationBorderClass *klass)
|
|||
g_object_class_install_property (object_class, PROP_RADIUS_Y,
|
||||
g_param_spec_int ("radius-y",
|
||||
"Radius Y",
|
||||
"Border radius in Y diection",
|
||||
"Border radius in Y direction",
|
||||
1, 2342, 1,
|
||||
G_PARAM_READWRITE |
|
||||
G_PARAM_CONSTRUCT));
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@ gimp_operation_shrink_class_init (GimpOperationShrinkClass *klass)
|
|||
g_object_class_install_property (object_class, PROP_RADIUS_X,
|
||||
g_param_spec_int ("radius-x",
|
||||
"Radius X",
|
||||
"Shrink radius in X diection",
|
||||
"Shrink radius in X direction",
|
||||
1, 2342, 1,
|
||||
G_PARAM_READWRITE |
|
||||
G_PARAM_CONSTRUCT));
|
||||
|
|
@ -106,7 +106,7 @@ gimp_operation_shrink_class_init (GimpOperationShrinkClass *klass)
|
|||
g_object_class_install_property (object_class, PROP_RADIUS_Y,
|
||||
g_param_spec_int ("radius-y",
|
||||
"Radius Y",
|
||||
"Shrink radius in Y diection",
|
||||
"Shrink radius in Y direction",
|
||||
1, 2342, 1,
|
||||
G_PARAM_READWRITE |
|
||||
G_PARAM_CONSTRUCT));
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@ cd <path-to-gimp-repo>/flatpak/build
|
|||
podman run --rm --privileged -v "$(pwd):/run/host:rw" ghcr.io/flathub/flatpak-external-data-checker:latest /run/host/org.gimp.GIMP-nightly.json
|
||||
```
|
||||
|
||||
Our prefered backend for the checker is Anitya, a database maintained
|
||||
Our preferred backend for the checker is Anitya, a database maintained
|
||||
by the Fedora project. To set up a new dependency check by Anitya:
|
||||
|
||||
1. verify it is available in the database: https://release-monitoring.org/
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Base rule to update the "GIMP (Preview)" entry:
|
|||
|
||||
1. The link above will open 'Partner Center', the frontend to submit .msixupload
|
||||
|
||||
2. With your Microsoft Entra ID account (@*onmicrosoft.com), log-in as costumary
|
||||
2. With your Microsoft Entra ID account (@*onmicrosoft.com), log-in as customary
|
||||
|
||||
3. Clicking on the "Start update" button will make possible to change some things.
|
||||
Only 'Packages' and 'Store listings' sections are needed. On 'Packages' you will
|
||||
|
|
|
|||
|
|
@ -191,7 +191,7 @@
|
|||
|
||||
<li>Floating selections not created anymore when pasting new layers</li>
|
||||
<li>New "Gray" theme based on a 18.42% luminance middle-gray background</li>
|
||||
<li>Icon sizes can be overriden in Preferences > Themes</li>
|
||||
<li>Icon sizes can be overridden in Preferences > Themes</li>
|
||||
|
||||
<li>Faster save of XCF files</li>
|
||||
<li>XCF file format improved with a proper structure for path items</li>
|
||||
|
|
|
|||
|
|
@ -209,7 +209,7 @@ A plugin may have a resource as a parameter.
|
|||
An interactive plugin may show a chooser widget to let a user choose a resource.
|
||||
The user's choices may be saved in settings.
|
||||
|
||||
In the same sesssion of GIMP, or in a subsequent session,
|
||||
In the same session of GIMP, or in a subsequent session,
|
||||
a user may invoke the plugin again.
|
||||
Then the saved settings are displayed in the plugin's dialog
|
||||
(when the second invocation is also interactive).
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ state. If this happens, you'd be advised to close and reopen the file
|
|||
|
||||
Another downside of plug-ins is that GIMP currently doesn't have any
|
||||
sandboxing ability. Since we explained that plug-ins are run by GIMP as
|
||||
independant processes, it also means they have the same rights as your
|
||||
independent processes, it also means they have the same rights as your
|
||||
GIMP process. Therefore be careful that you trust the source of your
|
||||
plug-ins. You should never run shady plug-ins from untrusted sources.
|
||||
|
||||
|
|
@ -258,7 +258,7 @@ rules. To do so:
|
|||
GIMP interface the widget you are interested to style;
|
||||
* the widget name will be displayed on the top of the information area
|
||||
of the dialog.
|
||||
* Feel free to browse the various sections to see the class hierachy,
|
||||
* Feel free to browse the various sections to see the class hierarchy,
|
||||
CSS nodes and so on.
|
||||
* The second top-left button (just next to the target icon) allows you
|
||||
to switch between the details of the selected widget and the widget
|
||||
|
|
@ -489,7 +489,7 @@ be considered as some kind dependency rule and should be updated.
|
|||
The `XCF` format is the core image format of GIMP, which mirrors
|
||||
features made available in GIMP. More than an image format, you may
|
||||
consider it as a work or project format, as it is not made for finale
|
||||
presentation of an artwork but for the work-in-progress processus.
|
||||
presentation of an artwork but for the work-in-progress process.
|
||||
|
||||
Developers are welcome to read the [specifications of XCF](https://developer.gimp.org/core/standards/xcf/).
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ The Symbolic icon theme is our main target since they are considered
|
|||
better suited for graphics work (less visual distraction). Color icons
|
||||
are kept as fall-back since some users prefer them.
|
||||
|
||||
Vector icons are now prefered because they are much less maintenance.
|
||||
Vector icons are now preferred because they are much less maintenance.
|
||||
For instance, we do not need to double, triple (or more) every icon for
|
||||
the various sizes they are needed in, and double this amount again to
|
||||
handle high density displays.
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ text file is enough to indicate what interpreter to start.
|
|||
On Windows (and Linux for Lua), you also need an .interp file installed with GIMP.
|
||||
|
||||
It can get complicated;
|
||||
there are many combinations of envirnoment variables, shebangs, file suffixes, and .interp files that can work.
|
||||
there are many combinations of environment variables, shebangs, file suffixes, and .interp files that can work.
|
||||
|
||||
*To insure a GIMP interpreted plugin works across platforms,
|
||||
it should have a shebang.*
|
||||
|
|
@ -30,7 +30,7 @@ since the ScriptFu extension reads them.*
|
|||
|
||||
## Partial history of interpreters in GIMP
|
||||
|
||||
Rarely are interpreters addded to GIMP.
|
||||
Rarely are interpreters added to GIMP.
|
||||
GIMP 2 offers Perl, Scheme, and Python2 interpreters.
|
||||
GIMP 3 offers Python3, lua, javascript, and the gimp-script-fu-interpreter interpreters.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
# Similarly to libgimpthumb/gimpthumb-enums.c, libgimp/gimpenums.c is
|
||||
# not versionned so we don't use the mkenums_wrap.
|
||||
# not versioned so we don't use the mkenums_wrap.
|
||||
# Moreover it is generated in 2 steps, first with common mkenums
|
||||
# arguments, then concatenating with a "tail" file.
|
||||
gimpenums_notail = custom_target('gimpenums.c.notail',
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
# Unlike other enums file, we don't use the mkenums_wrap because this
|
||||
# one is not versionned in the repository (not sure why). Moreover the
|
||||
# one is not versioned in the repository (not sure why). Moreover the
|
||||
# options are quite different from the other generated enums, so it
|
||||
# didn't make sense to overdo it.
|
||||
gimpthumbenums = custom_target('gimpthumb-enums.c',
|
||||
|
|
|
|||
|
|
@ -184,7 +184,7 @@ optimize_create_procedure (GimpPlugIn *plug_in,
|
|||
"final file size. If a frame of the"
|
||||
"animation can use the 'combine' "
|
||||
"mode, this procedure attempts to "
|
||||
"maximize the number of ajdacent "
|
||||
"maximize the number of adjacent "
|
||||
"pixels having the same color, which"
|
||||
"improves the compression for some "
|
||||
"image formats such as GIF or MNG.",
|
||||
|
|
|
|||
|
|
@ -284,7 +284,7 @@ colorize_create_procedure (GimpPlugIn *plug_in,
|
|||
"This plug-in colorizes the contents of the specified (gray) layer"
|
||||
" with the help of a sample (color) layer."
|
||||
" It analyzes all colors in the sample layer."
|
||||
" The sample colors are sorted by brightness (== intentisty) and amount"
|
||||
" The sample colors are sorted by brightness (== intensity) and amount"
|
||||
" and stored in a sample colortable (where brightness is the index)"
|
||||
" The pixels of the destination layer are remapped with the help of the"
|
||||
" sample colortable. If use_subcolors is TRUE, the remapping process uses"
|
||||
|
|
|
|||
|
|
@ -1058,7 +1058,7 @@ parse_control_point (char **ss,
|
|||
}
|
||||
else if (! g_ascii_string_to_signed (argv[i++], 10, 1, GIMP_MAX_IMAGE_SIZE, &h, NULL))
|
||||
{
|
||||
g_printerr ("Ignoring invalid image_size heigth '%s'\n", argv[i-1]);
|
||||
g_printerr ("Ignoring invalid image_size height '%s'\n", argv[i-1]);
|
||||
parse_errors++;
|
||||
}
|
||||
else
|
||||
|
|
|
|||
|
|
@ -118,7 +118,7 @@ A directory containing an .scm file queried by script-fu-interpreter
|
|||
is usually a subdirectory of one of the /plug-ins directories,
|
||||
unlike for extension-script-fu, where the .scm files are in a /scripts dir.
|
||||
|
||||
A plugin directory should contain only one queriable .scm file:
|
||||
A plugin directory should contain only one queryable .scm file:
|
||||
only one file can have the same base name as the directory and
|
||||
GIMP will query that file.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Changelog:
|
|||
WHAT IS TSX?
|
||||
|
||||
TinyScheme Extensions is a set of dynamic libraries incorporating
|
||||
additional funcionality to TinyScheme, a lightweight
|
||||
additional functionality to TinyScheme, a lightweight
|
||||
implementation of the Scheme programming language. TinyScheme
|
||||
(http://tinyscheme.sourceforge.net) is maintained by D. Souflis
|
||||
(dsouflis@acm.org), and is based on MiniSCHEME version 0.85k4.
|
||||
|
|
|
|||
|
|
@ -51,4 +51,4 @@ The number of bytes in a string can be had with libc strlen().
|
|||
|
||||
## Other forks
|
||||
|
||||
Anothers signficant fork of upstream TinyScheme is in the gnupgp project, where it scripts tests.
|
||||
Another significant fork of upstream TinyScheme is in the gnupgp project, where it scripts tests.
|
||||
|
|
@ -76,7 +76,7 @@
|
|||
;
|
||||
; (+ (random 15) 1) yields [2, 16] uniform.
|
||||
; The original formula, a product of random numbers, yields [3, 255] non-uniform.
|
||||
; To accomodate changes to distress-selection, we use the old formula, and divide by 255.
|
||||
; To accommodate changes to distress-selection, we use the old formula, and divide by 255.
|
||||
; When you instead just generate a single random float, stains are smaller.
|
||||
(set! theThreshold (/
|
||||
(- (* (+ (random 15) 1) (+ (random 15) 1)) 1) ; original formula
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
; See instruction on adding new exporters at the end
|
||||
;
|
||||
|
||||
; !!! Here run functions call script-fu-use-v3, to bind PDB returns succintly.
|
||||
; !!! Here run functions call script-fu-use-v3, to bind PDB returns succinctly.
|
||||
|
||||
; -----------------------------------------------------------------------------
|
||||
; Numbers and Math
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@
|
|||
; call a script that always fails
|
||||
(script-fu-always-fail)
|
||||
; we have not checked the result and declaring the error on our own.
|
||||
; since this is the last expression, the #f from the call should propogate.
|
||||
; since this is the last expression, the #f from the call should propagate.
|
||||
)
|
||||
|
||||
(script-fu-register "script-fu-call-always-fail"
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
; Test a .scm file that does not call script-fu-menu-register
|
||||
; The menu will NOT default.
|
||||
; Expect "Test SF interpreter 4" to NOT EXIST in any menu
|
||||
; Expect the PDB proc "script-fu-test4" does appear in the PDB Brower
|
||||
; Expect the PDB proc "script-fu-test4" does appear in the PDB Browser
|
||||
|
||||
; Two test cases:
|
||||
; Alongside an executable script: plug-ins/test4/test4.scm NOT executable
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
|
||||
; Seems not used by any script in the repo.
|
||||
; FUTURE move to gimp-data-extras or to scripts/test
|
||||
; and maintain it with low priorty.
|
||||
; and maintain it with low priority.
|
||||
|
||||
; unsharp-mask is a filter AND renderer, creating a new, visible, dirty image
|
||||
; from the given image.
|
||||
|
|
|
|||
|
|
@ -253,7 +253,7 @@
|
|||
; expected-error)
|
||||
|
||||
|
||||
; Statments in the testing DSL.
|
||||
; Statements in the testing DSL.
|
||||
|
||||
; The usual or normal test.
|
||||
; <code> is a boolean proposition expected to yield #t
|
||||
|
|
@ -436,7 +436,7 @@
|
|||
|
||||
; Returns path to file containing named color profile
|
||||
; Currently, assumes color profiles downloaded to /work dir.
|
||||
; FUTURE: platform indpendent path
|
||||
; FUTURE: platform independent path
|
||||
; FUTURE: color profile test files in the repo
|
||||
(define (testing:path-to-color-profile name)
|
||||
(string-append "/work/" name))
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@ test_scripts = [
|
|||
]
|
||||
|
||||
# Install test framework to shared /scripts
|
||||
# Assert: SFConsole, SFExtension, and standalong SFInterpreter will read them.
|
||||
# Assert: SFConsole, SFExtension, and standalone SFInterpreter will read them.
|
||||
# SFConsole is primary testing interface.
|
||||
# Some plugins in /scripts (SFExtension)
|
||||
# and in /plug-ins (SFInterpreter) may also be interface for testing.
|
||||
|
|
|
|||
|
|
@ -93,8 +93,8 @@
|
|||
'(255)))
|
||||
|
||||
; a color from a grayscale with alpha image is a list of one
|
||||
; For gimp-logo.png the backround is 0 i.e. black
|
||||
; For wilber.png the backround is 71 some intermediate gray
|
||||
; For gimp-logo.png the background is 0 i.e. black
|
||||
; For wilber.png the background is 71 some intermediate gray
|
||||
; FIXME, why do two images rgba converted to gray and flattened
|
||||
; have different values for a total transparent pixel?
|
||||
(assert `(equal? (gimp-drawable-get-pixel ,testDrawableGrayA 1 1)
|
||||
|
|
@ -216,7 +216,7 @@
|
|||
|
||||
|
||||
(test! "Extra components in colors")
|
||||
; lenth 5, only 4 components used
|
||||
; length 5, only 4 components used
|
||||
(assert `(gimp-context-set-background '(0 0 0 0 5)))
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@
|
|||
|
||||
|
||||
; get bounding box of intersection of selection mask with drawable
|
||||
; bounding box in x, y, width, heigth format
|
||||
; bounding box in x, y, width, height format
|
||||
(assert `(gimp-drawable-mask-bounds ,testDrawable))
|
||||
; bounding box in upper left x,y lower right x,y
|
||||
(assert `(gimp-drawable-mask-intersect ,testDrawable))
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
; Tests in alphabetic order of attribute name
|
||||
|
||||
; Assymmetry:
|
||||
; Asymmetry:
|
||||
; - some attributes can be get, but not set
|
||||
; - some attributes can be set but not get
|
||||
; Such attributes are set only in libgimp, not by a PDB procedure
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
; That is, we don't render the image and have a human look at the results.
|
||||
; Also, there is no API for programmatically finding what rendered colors are out of gamut.
|
||||
; Also, there is no API for programmatically rendering under the simulation profile.
|
||||
; i.e. like the user would do under View>Color Managment>SoftProof.
|
||||
; i.e. like the user would do under View>Color Management>SoftProof.
|
||||
|
||||
; Notes about test data, all binary files
|
||||
; name vector file MODE
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@
|
|||
; TODO test multi-select, a set of two member path
|
||||
|
||||
; The generic getter get-selected-drawables
|
||||
; Returns a homogenous vector of previously selected channels.
|
||||
; Returns a homogeneous vector of previously selected channels.
|
||||
(assert `(= (vector-ref (car (gimp-image-get-selected-drawables ,testImage)) 0)
|
||||
,testChannel))
|
||||
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@
|
|||
|
||||
; gimp module, gimp-get methods
|
||||
(testing:load-test "gimp.scm")
|
||||
; gimp PDB as a queriable store i.e. database
|
||||
; gimp PDB as a queryable store i.e. database
|
||||
(testing:load-test "PDB.scm")
|
||||
; test gimp as a refreshable set of installed resources
|
||||
(testing:load-test "refresh.scm")
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@
|
|||
; is a flag indicating whether *user or program* has
|
||||
; set the selection since calling select-none.
|
||||
|
||||
; Wierd case: 0 width should throw out of bounds error?
|
||||
; Weird case: 0 width should throw out of bounds error?
|
||||
|
||||
; selecting a zero width rect does not throw an error
|
||||
(assert `(gimp-image-select-rectangle
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@
|
|||
|
||||
; export all paths to string all succeeds
|
||||
; passing 0 for path means "all"
|
||||
; FIXME this is wierd, should be a separate method gimp-image-export-paths-to-string
|
||||
; FIXME this is weird, should be a separate method gimp-image-export-paths-to-string
|
||||
; The name implies a single path
|
||||
(assert `(gimp-image-export-path-to-string
|
||||
,testImage
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@
|
|||
;(assert-error `(close-port ,aOutFilePort)
|
||||
; "Error: not a port")
|
||||
|
||||
; aOutFilePort is still in scope and shoud not be garbage collected.
|
||||
; aOutFilePort is still in scope and should not be garbage collected.
|
||||
|
||||
(test! "A closed port is still a port")
|
||||
(assert `(port? ,aOutFilePort))
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@
|
|||
; e.g. export LANG="de_DE.UTF-8"
|
||||
; In that locale, comma is used as a decimal point.
|
||||
; In TinyScheme, string representation of numbers SHOULD use period as decimal point.
|
||||
; But currently doesn't, in some locales using comman for decimal point.
|
||||
; But currently doesn't, in some locales using comma for decimal point.
|
||||
; Because TinyScheme uses C standard lib snprintf
|
||||
; which respects locale and can print comma for decimal point.
|
||||
|
||||
|
|
|
|||
|
|
@ -46,12 +46,12 @@
|
|||
(assert '(equal? (integer->char 13) #\return))
|
||||
(assert '(equal? (integer->char 32) #\space))
|
||||
|
||||
; Mispelled sharp constants
|
||||
; Misspelled sharp constants
|
||||
; Any sequence of chars starting with #\n, up to a delimiter,
|
||||
; that does not match "newline"
|
||||
; is parsed as the sharp constant for the lower case ASCII n char.\
|
||||
; Similarly for tab, return, space
|
||||
(test! "mispelled sharp char constant for newline")
|
||||
(test! "misspelled sharp char constant for newline")
|
||||
; 110 is the codepoint for lower case n
|
||||
(assert '(equal? (integer->char 110) #\n))
|
||||
(assert '(equal? (integer->char 110) #\newlin))
|
||||
|
|
|
|||
|
|
@ -197,7 +197,7 @@
|
|||
|
||||
(test! "read-byte then read-char on input-string, two-byte UTF-8 encoded char")
|
||||
; The first byte of the lambda char is 0xce 206, the next 0xbb 187, code point is 0x3bb
|
||||
; Expect this leaves the port in condtion for a subsequent read-char or read
|
||||
; Expect this leaves the port in condition for a subsequent read-char or read
|
||||
(assert `(= (byte->integer (read-byte ,aStringPort))
|
||||
206))
|
||||
(assert `(= (byte->integer (read-byte ,aStringPort))
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@
|
|||
|
||||
|
||||
|
||||
; assert-error statment
|
||||
; assert-error statement
|
||||
|
||||
; assert-error tests for error messages
|
||||
; assert-error omits the "Error: " prefix printed by the REPL
|
||||
|
|
|
|||
|
|
@ -26,13 +26,13 @@
|
|||
|
||||
/* Background color for hovered items to "stick out". */
|
||||
@define-color hover-color rgb(100,100,100);
|
||||
/* Background color when we want widgets-in-widgets to differenciate. It
|
||||
/* Background color when we want widgets-in-widgets to differentiate. It
|
||||
* will usually be "less extreme", i.e. darker on a light theme, or
|
||||
* lighter on a dark theme.
|
||||
*/
|
||||
@define-color widget-bg-color rgb(42,42,42);
|
||||
/* Color for selected items, in particular when their usual background
|
||||
* color is @widget-bg-color or @bg-color. It will usually be ligher on
|
||||
* color is @widget-bg-color or @bg-color. It will usually be lighter on
|
||||
* a light theme, or darker on a dark theme.
|
||||
*/
|
||||
@define-color selected-color rgb(30,30,30);
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
#!/bin/bash
|
||||
|
||||
# This is a very basic script for developper usage. It has a few known
|
||||
# This is a very basic script for developer usage. It has a few known
|
||||
# limitations (feel free to send patches for these):
|
||||
# - It is targetted at GIMP usage primarily, hence able to check only
|
||||
# - It is targeted at GIMP usage primarily, hence able to check only
|
||||
# Flathub (stable and beta remotes) and GNOME-nightly. Yet some
|
||||
# generity is built-in so you can set your own application ID on
|
||||
# command line and it should work.
|
||||
|
|
@ -46,7 +46,7 @@ do
|
|||
echo
|
||||
echo "List all flatpak builds stored on Flathub or GNOME repository."
|
||||
echo "The builds for org.gimp.GIMP are looked up by default unless"
|
||||
echo "you provide explicitely another AppStream ID."
|
||||
echo "you provide explicitly another AppStream ID."
|
||||
echo
|
||||
echo "Adding a -X number as option install the numbered release"
|
||||
echo "instead of listing them."
|
||||
|
|
@ -67,7 +67,7 @@ do
|
|||
echo
|
||||
echo "Examples:"
|
||||
echo
|
||||
echo "* List all beta flatpak bulds:"
|
||||
echo "* List all beta flatpak builds:"
|
||||
echo " flathub-releases --beta"
|
||||
echo "* Install 2-build old beta flatpak:"
|
||||
echo "* flathub-releases --beta -2"
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
# This is a wrapper to the tools/gimp-mkenums perl script which:
|
||||
# * sets a few common values;
|
||||
# * updates the ${filebase}enums.c directly in the source directory in
|
||||
# order for it to be versionned.
|
||||
# order for it to be versioned.
|
||||
# * Create a no-op stamp-header file to be included by the resulting
|
||||
# enums.c. The goal is to make sure that meson will trigger a rebuild
|
||||
# of the enums.c generation before compiling, if the enums.h changed.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue