aboutsummaryrefslogtreecommitdiffstatshomepage
Commit message (Collapse)AuthorAgeLines
* po: Do not break long message linesWolfgang Müller2021-11-27-2/+2
| | | | | | | | Both xgettext(1) and msgmerge(1) break messages by default. Since we currently do not have particularly long strings marked for translation, turn this particular behaviour off by passing --no-wrap. It would otherwise lead to spurious breaks in the PO and POT files that are not particularly nice.
* Don't consider punctuation as part of the URLJuhani Krekelä2021-11-27-1/+1
| | | | | | | | | | | | We currently consider periods, commas, colons, semicolons, exclamation points and question marks following a URL as part of it. While ending a URL with these characters is technically speaking valid, more commonly they are a result of people ending a clause with a URL. Let's ignore such characters if they are present at the very end of a URL. Make sure to still match them, however, if any non-punctuation characters follow. This way, almost all actual usage of punctuation within URLs is unaffected.
* Update German translation of the manualWolfgang Müller2021-11-27-1/+19
| | | | | Describe the "Open with…" feature here as well and make sure to update the sample configuration file with the new section.
* po: Update German translationWolfgang Müller2021-11-27-6/+6
|
* po: Update Finnish translationJuhani Krekelä2021-11-27-4/+4
|
* Add ability to specify additional URI handlersJuhani Krekelä2021-11-27-38/+196
| | | | | | | | | This commit adds a new section, open-with, to the configuration file. The options specified there will be added as "Open with …" menu items in the URI context menu. This is to make it easier to perform other actions on the URI than opening it in the system default browser; a user might for example add another browser, media player, or a script that preprocesses the URI before opening it.
* po: Fix update-pot.sh breaking on non-ASCIIJuhani Krekelä2021-11-27-1/+1
| | | | | | | Currently po/update-pot.sh assumes English strings and translator comments cannot contain characters outside of ASCII, and throws an error upon encountering any. Since we are actually using UTF-8 and not ASCII, tell xgettext so.
* Move spawning a subprocess into its own functionJuhani Krekelä2021-07-24-7/+10
| | | | | | The upcoming "Open with …" feature will need to spawn subprocesses in very similar way as open_terminal(). Moving process creation to its own function allows the same logic to be reused.
* Unify context menus for URLs and OSC 8 hyperlinksJuhani Krekelä2021-07-24-110/+60
| | | | | | | | | | | Currently weltschmerz has separate context menus for the two types of URIs one can interact with, even though they contain the same option with only a little different phrasing. This makes both use the same context menu, and standardizes terminology to "URI". This unification is in preparation for an upcoming "Open with …" feature which will programmatically add items to context menu for URIs. Without this, we would need to duplicate logic for each of the separate menus.
* Prepare release of version 1.4.11.4.1Wolfgang Müller2021-07-16-0/+15
|
* Install translated manualsWolfgang Müller2021-07-15-1/+12
| | | | | | | | | | With at least one manual now fully translated, we need to install it to the right place in both the Makefile and meson.build. For the former use a similar loop as is in use for the MO files. For the latter we sadly need to place the manual manually using install_data() because meson only supports localized manuals natively starting at 0.58.0, a version that is only about two months old.
* Add German translation of the manualWolfgang Müller2021-07-15-0/+291
|
* Mention overlay scrolling in the manualWolfgang Müller2021-07-12-1/+13
| | | | | | GTK's decision to make overlay scrolling the default seems to be quite controversial. It also brings with it added complexity in both behaviour and configuration and should therefore be mentioned in the manual.
* Add support for gopher:// URLsJuhani Krekelä2021-07-09-1/+1
|
* Improve URL matchingJuhani Krekelä2021-07-09-1/+1
| | | | | | | | | | | | | Currently the weltschmerz URL regex does not match URLs with quotes or parentheses, considering the URL to end when one is encountered. On the other hand, if a URL is surrounded by angle brackets it includes the closing '>' in the URL match. Additionally, the regex allows URL to contain a space if and only if it is the second character of the host component of the URL. Most of this appears to be down to bugs in the regex as it is currently written. This rewrites the regex to be cleaner and easier to read, while maintaining the intended logic of the original.
* Prepare release of version 1.4.01.4.0Wolfgang Müller2021-07-03-0/+42
|
* Only allow opening local directoriesJuhani Krekelä2021-07-02-2/+11
| | | | | | | | | | | | | | | | | | | The proposed OSC 7 specification mandates [1] that the file:// URI includes the hostname, so that the terminal emulator can ignore remotely used programs' attempts to set the current working directory. However, VTE does not check the hostname component, and neither does launch_default_for_uri. Thus currently if one tries to open directory after running a remote program that used OSC 7, weltschmerz tries to open a file manager pointing at corresponding path on the local computer. weltschmerz already contains a function that checks the URI kept by VTE and returns the path only if it is on the local computer. This commit changes open_directory() to first use that, and then create a new local file:// URI based on it, unifying the behaviour of 'Open directory' and 'Open terminal'. [1] https://gitlab.freedesktop.org/terminal-wg/specifications/-/issues/20#note_294252
* po: Introduce more robust error handlingWolfgang Müller2021-07-02-0/+6
| | | | | | | | This commit enables 'errexit' for both shell scripts in po/, ensuring that no further action is taken should one of the commands fail. init-po.sh now tests for the presence of a language code and refuses to continue if none is given.
* Clean up .gitignoreWolfgang Müller2021-06-29-3/+3
| | | | | No effective functional change. Make sure that rules are anchored to the top level.
* Use custom scripts instead of meson's gettext toolingWolfgang Müller2021-06-29-27/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | meson's tooling for gettext introduces a couple of issues. Firstly, it is currently not possible [1] to specify per-language keywords. We need this in order to ignore the 'Name' record in the desktop file. Secondly, every invocation of 'update-po' also updates the pot file [2], inadvertently recording the updated creation date in all translations. Since we recommended the use of 'update-po' to translators in TRANSLATE, this will lead to lots of unrelated changes every time a new translation is added, even if no msgids change. Thirdly, people who do not have meson installed are currently not able to use the tooling it provides. To fix these issues, this commit adds custom tooling around gettext: The 'update-pot.sh' script updates the pot and po files using xgettext(1) and msgmerge(1), and 'init-po.sh' makes the necessary changes to LINGUAS whilst also creating the relevant po file(s) with msginit(1). We no longer need to refer to meson at all in TRANSLATE. Make sure to mention the new scripts as well. [1] https://github.com/mesonbuild/meson/issues/1739 [2] https://github.com/mesonbuild/meson/blob/a9e9b7c7501a3c8a5984a93879d1f309bf8c72aa/mesonbuild/scripts/gettext.py#L112
* po: Add Finnish translationJuhani Krekelä2021-06-28-1/+115
|
* Add TRANSLATE fileWolfgang Müller2021-06-28-0/+59
| | | | | Translators may not be familiar with the code base or translation process. This commit adds a small guide detailing common steps.
* Make Makefile portableJuhani Krekelä2021-06-28-2/+5
| | | | | | | | | Currently weltschmerz's make-based build system relies on GNU make extensions. Change it to only use POSIX and other nearly universally implemented features. A small downside to this patch is that .po files must be listed in the Makefile manually.
* Build localization files when running `make all`Juhani Krekelä2021-06-28-2/+4
| | | | | | | | | Currently these localization files are only built when the user executes `make install`. Since `make install` is often run as root, this leaves files with root as their owner in the source directory. There are also security implications to running compilers as root. This patch adds a target `all` to the Makefile which depends on the localization files, so that they are built as the user.
* po: Add German translationWolfgang Müller2021-06-28-0/+114
|
* po: Specify UTF-8 for all potential input to xgettextWolfgang Müller2021-06-28-1/+1
| | | | | Since the default setting of ASCII-only could potentially bite us in the long run, make sure to have xgettext interpret files as UTF-8.
* po: Add portable object templateWolfgang Müller2021-06-28-0/+113
| | | | | | | This is the mail .pot file that all future translations will use as a base. Since the header is supposed to be filled out by translators in the .po file, we can leave it as-is. This also makes subsequent updates to this file easier, since it is generated by a tool.
* po: Add translatable files to POTFILESWolfgang Müller2021-06-27-0/+4
|
* Mark messages for translationWolfgang Müller2021-06-27-9/+16
| | | | | | | | | | | | | | | | With the translation infrastructure now in place, make sure to mark every user-bound message for translation. All but one of the strings in terminal.ui are already marked. This commit marks all remaining messages in the Vala code as well as the missing one from terminal.ui. One of the messages in terminal.ui is a sample error message for the infobar label. Since this message will never be visible to the user (the code overrides the label's contents with any relevant warning messages), we do not need to keep it marked. Finally, give translators ample context for what they will have to translate and fix a small inconsistency with the capitalization of warning messages in configreader.vala.
* po: Specify comment tag for xgettextWolfgang Müller2021-06-27-1/+3
| | | | | | | | | For some translatable strings we need to provide more context to the translators. Conveniently, xgettext [1] provides the '-c[tag]' flag for this. Make sure to pass along any comment containing "TRANSLATORS" preceding a gettext call to the .pot file. [1] https://www.gnu.org/software/gettext/manual/html_node/xgettext-Invocation.html
* Prepare for internationalizationWolfgang Müller2021-06-27-4/+44
| | | | | | | | | | | | | | | | | | | | | | | | | weltschmerz currently does not allow for translation and exists in English only. This is a serious defect for people who do not speak that language. The following series of commits aims to remedy this by adding the necessary infrastructure and build steps to enable easy translation. To do this we use GNU gettext[1]; its tooling is widely supported and a de-facto standard. Since we need to tell gettext where to find the compiled .mo translation files, have both the Makefile and meson pass the locale directory to weltschmerz in form of a LOCALEDIR macro. The translation domain will be "weltschmerz". Not only will any strings in the Vala code have to be translated, we need to make sure to translate terminal.ui and weltschmerz.desktop as well. The former will be taken care of through POTFILES only, but for the latter we have to define an intermediary build step. To ensure compatibility with the Makefile, we suffix the desktop file with '.in'. For now, LINGUAS and POTFILES remain empty. A future commit will document all files needing translation. LINGUAS will be updated as translations are completed. [1] https://www.gnu.org/software/gettext
* Add feature to open a new terminalJuhani Krekelä2021-06-26-1/+74
| | | | | | | | | | | | | | | | | | | | | | Add ability to open a new weltschmerz terminal, either from context menu or with a key combination. The new terminal is opened in the directory indicated with OSC 7, allowing quickly opening additional terminals while working. Preferably this would launch the user's preferred terminal, as defined in per-user settings, but this is not possible with glib[1]. For this reason the option always launches another weltschmerz. weltschmerz is launched using bare Process.spawn_async() on the name of the program as defined in weltschmerz.vala. We considered using the AppInfo database to retrieve the name of executable instead, but as there is no way to query the database for terminal emulators we would have to go through every single program installed on the computer and try to find one called weltschmerz. As the change would merely replace the requirement of having weltschmerz in PATH with the requirement of having a .desktop file with the name in one of the standardized locations, this would not be worth it. [1] https://gitlab.gnome.org/GNOME/glib/-/issues/338
* Copy URLs to the PRIMARY selection as wellWolfgang Müller2021-06-25-0/+4
| | | | | | | | | Currently, weltschmerz only copies URLs to GTK's default clipboard. This is defined to be CLIPBOARD, leaving the PRIMARY selection unchanged. Since all other normal copy/paste operations start with making a selection and therefore set PRIMARY, make sure to also set the PRIMARY selection when copying a URL. This brings weltschmerz in line with how other GTK apps behave.
* Use fallback 'html' value for vte_copy() in vte_key_press()Wolfgang Müller2021-06-25-1/+1
| | | | | | No functional change, since vte_copy() defaults to false here. This seems to be a remnant of when vte_copy() required specifying the 'html' argument.
* Define a reasonable minimum sizeWolfgang Müller2021-06-23-4/+6
| | | | | | | | | | | | | | | | | | | | | Previously, in commit c49fbfb (Set minimum width and height in window geometry, 2021-06-17), we set the minimum size of the window to one cell. We do not yet include our fixes from 89f8571 (Calculate base_width dynamically, 2021-06-18) and so do not account for the scrollbar when setting the minimum size hints. A minimum size of one cell can lead to issues like [1] when resizing aggressively. A fix for this has been committed in [2], but not yet merged to any release branch. Setting the minimum size to larger values seems to work around this problem. Therefore, define a minimum window size of 28 x 3 cells - just big enough to still fit the search overlay. Make sure to include base_height and base_width so that the right size will be reported to the window manager. [1] https://gitlab.gnome.org/GNOME/vte/-/issues/340 [2] https://gitlab.gnome.org/GNOME/vte/-/commit/b333d66879963637099dc0bc5a702f50f34da67e
* Update TODO with relevant info on issues with GtkScrolledWindowWolfgang Müller2021-06-22-2/+6
|
* Clean up and slightly reorganize load_config()Wolfgang Müller2021-06-19-3/+1
|
* Mark env_shell as unownedWolfgang Müller2021-06-19-2/+2
| | | | | | The Environment.get_variable() method returns an unowned value. Make sure to mark it as such in our code. Whilst we're here, add a missing space to the subsequent if branch.
* Calculate base_width dynamicallyWolfgang Müller2021-06-19-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | weltschmerz sets window geometry hints to indicate how the terminal window is to be sized and resized. New sizes are always kept at a multiple of the character width and height. Effectively, this ensures that terminal windows never have "negative space" that is not used for any terminal output. In order to account for padding and non-terminal widgets, one may specify base_height and base_width. These values indicate how much space to add in a final step, after the character width and heights have been multiplied with the amount of columns and rows respectively. For example, allowed window widths are always: (char_width * N) + base_width Currently, we always use a base_width of 2 * 2. This is to account for the padding of 2 pixels as specified in terminal.css. weltschmerz uses GtkScrolledWindow and overlay scrolling by default. With overlay_scrolling enabled, the scrollbar does not take up any extra space. The previous commit works around a problem with GtkScrolledWindow and sets PolicyType.ALWAYS when overlay scrolling is turned off. This means that we now also have to account for the size of that scrollbar. Since we cannot simply query the size of the scrollbar, we have to be a bit more creative. Use the full window width and subtract the width of the terminal at startup (we know it is always 80 columns) to get the amount of space taken up by "anything else". This includes VTE padding and the scrollbar size. Importantly, this needs only be done once and is completely agnostic to any further changes to the terminal or font size (which affects the cell width and height). We only assume that both the size of the scrollbar and the amount of padding is constant, which we feel to be a reasonable trade-off.
* Always draw the scrollbar if overlay scrolling is offWolfgang Müller2021-06-19-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | weltschmerz uses GtkScrolledWindow to provide a vertical scrollbar to the user. By default, this widget enables overlay scrolling. This means that the scrollbar is painted "inside" the terminal, as if overlaid. There's no configuration switch to turn this behaviour off, since we are convinced that overlay scrolling is the right thing to do for terminals. However, GTK allows users to turn off overlay scrolling in a global setting [1] or by using the 'GTK_OVERLAY_SCROLLING' environment variable. Some distributions turn overlay scrolling off by default. When overlay scrolling is disabled, GtkScrolledWindow falls back to rendering the scrollbar normally. Since our scrollbar policy is set to AUTOMATIC, it is only drawn on demand. This means that it is initially not be visible but can suddenly take up effective window space once it appears. When this happens, depending on what is going on in the terminal, one can be left with a terminal that is scrolling down infinitely as the reported column width flaps between two values: one accounting for the size of the scrollbar and the other one ignoring it. Each time the column width flaps, VTE sends SIGWINCH, possibly getting caught in an infinite loop of internal resizes. Since upstream declares GtkScrolledWindow incompatible with VTE [2] [3], we have not attempted further investigation on this issue, but may report an issue in the future. We definitely want to keep using GtkScrolledWindow even with this incompatibility - it is the most elegant and visually pleasing solution. The alternative would be to use a GtkBox and supply our own scrollbar. This scrollbar would either always be visible (even if there is nothing to scroll) or entirely hidden. An implementation of this may be found in the box-scroll branch. Note, however, that we do not guarantee that branch to be up to date with the latest developments. To work around this problem, detect when overlay scrolling is turned off and fall back to PolicyType.ALWAYS. This ensures that the scrollbar is always visible, mitigating the infinite resize loop. Crucially, compared to the alternative solution, this will still enable users to enjoy overlay scrolling if they (or their distribution) do not turn it off. [1] https://developer.gnome.org/gtk3/stable/GtkSettings.html#GtkSettings--gtk-overlay-scrolling [2] https://gitlab.gnome.org/GNOME/vte/-/issues/11#note_264921 [3] https://bugzilla.gnome.org/show_bug.cgi?id=733210#c2
* Always hide the horizontal scrollbarWolfgang Müller2021-06-19-1/+1
| | | | | Even though PolicyType.AUTOMATIC should always keep it hidden, be explicit about our wish to show it under no circumstances.
* Remove trailing comma from geometry initializerWolfgang Müller2021-06-19-1/+1
| | | | | | | | | | | | Commit c49fbfb (Set minimum width and height in window geometry, 2021-06-17) introduced a trailing comma to make subsequent changes to the initializer less of a hassle. However, Vala only accepts trailing commas starting with 0.52.3 [1]. It would be petty to require this version, especially since older versions of Vala can still compile weltschmerz without problems. [1] https://gitlab.gnome.org/GNOME/vala/-/commit/20fcf9ce42dca52c707b96ddf7457931d6ee96f5
* Add TODO item regarding the deprecation of GtkImageMenuItemWolfgang Müller2021-06-19-0/+9
|
* terminal.ui: Require at least GTK 3.24Wolfgang Müller2021-06-19-2/+1
| | | | | | | | | | | | GTK 3.24 is the last release for the GTK 3 series [1]. New development now only happens on GTK 4 and above. Therefore it is reasonable to require this long-term stable version of GTK 3 instead of an older candidate. Since 3.24 deprecates the 'window-placement-set' property, remove it fully as well. [1] https://blog.gtk.org/2018/06/23/a-gtk-3-update
* terminal.ui: Stop using 'margin-left' and 'margin-right' propertiesWolfgang Müller2021-06-19-2/+2
| | | | | | | These were deprecated in GTK 3.12 [1]. Instead use 'margin-start' and 'margin-end' for the same effect. [1] https://developer.gnome.org/gtk3/stable/GtkWidget.html#GtkWidget--margin-left
* terminal.ui: Remove deprecated 'shadow-type' propertyWolfgang Müller2021-06-18-1/+0
| | | | | | This property was deprecated in GTK 3.20 [1]. Remove it. [1] https://developer.gnome.org/gtk3/stable/GtkEntry.html#GtkEntry--shadow-type
* terminal.ui: Stop using deprecated 'stock' propertyWolfgang Müller2021-06-18-1/+1
| | | | | | | GTK-STOCK-OPEN was deprecated in GTK 3.10 [1]. Use the recommended named icon 'document-open' icon instead. [1] https://developer.gnome.org/gtk3/stable/gtk3-Stock-Items.html#GTK-STOCK-OPEN:CAPS
* terminal.ui: Update property names and sort objectsWolfgang Müller2021-06-18-154/+154
| | | | | This was done automatically by glade 3.38.2. There are no functional changes.
* Set minimum width and height in window geometryWolfgang Müller2021-06-18-3/+8
| | | | | | | | | weltschmerz currently does not indicate any minimum size for its window geometry. If the minimum size is not set, GtkWindow uses its requisition as the minimum size [1]. Make sure, instead, that we control this value and set it to one cell. [1] https://valadoc.org/gdk-3.0/Gdk.Geometry.html
* Add setting for controlling cursor blinkingJuhani Krekelä2021-06-17-1/+36
| | | | | | | | | | Currently weltschmerz always uses the global GTK setting for cursor blink, which means that the cursor blink setting is stored separately from the rest of the configuration. Add a setting for overriding it in the config file, so that all the relevant settings can be adjusted in one standardized place. Reviewed-by: Wolfgang Müller <wolf@oriole.systems>
powered by cgit and git | oriole.systems | how to verify signatures