rename VTE -> BTE

README.md

@@ -1,29 +1,29 @@
 Virtual TErminal
 ================
 
-VTE provides a virtual terminal widget for CTK applications.
+BTE provides a virtual terminal widget for CTK applications.
 
 Installation
 ------------
 
 ```
-$ git clone https://gitlab.gnome.org/GNOME/bte  # Get the source code of VTE
+$ git clone https://gitlab.gnome.org/GNOME/bte  # Get the source code of BTE
 $ cd bte                                        # Change to the toplevel directory
 $ meson _build                                  # Run the configure script
-$ ninja -C _build                               # Build VTE
+$ ninja -C _build                               # Build BTE
 [ Optional ]
-$ ninja -C _build install                       # Install VTE to default `/usr/local`
+$ ninja -C _build install                       # Install BTE to default `/usr/local`
 ```
 
-* By default, VTE will install under `/usr/local`. You can customize the
-prefix directory by `--prefix` option, e.g. If you want to install VTE under
+* By default, BTE will install under `/usr/local`. You can customize the
+prefix directory by `--prefix` option, e.g. If you want to install BTE under
 `~/foobar`, you should run `meson _build --prefix=~/foobar`. If you already
 run the configure script before, you should also pass `--reconfigure` option to it.
 
 * You may need to execute `ninja -C _build install` as root
 (i.e. `sudo ninja -C _build install`) if installing to system directories.
 
-* If you wish to test VTE before installing it, you may execute it directly from
+* If you wish to test BTE before installing it, you may execute it directly from
 its build directory. As `_build` directory, it should be `_build/src/app/bte-[version]`.
 
 * You can pass `-Ddebugg=true` option to meson if you wish to enable debug function.
@@ -32,18 +32,18 @@ its build directory. As `_build` directory, it should be `_build/src/app/bte-[ve
 Debugging
 ---------
 
-After installing VTE with `-Ddebugg=true` flag, you can use `VTE_DEBUG` variable to control
-VTE to print out the debug information
+After installing BTE with `-Ddebugg=true` flag, you can use `BTE_DEBUG` variable to control
+BTE to print out the debug information
 
 ```
 # You should change bte-[2.91] to the version you build
-$ VTE_DEBUG=selection ./_build/src/app/bte-2.91
+$ BTE_DEBUG=selection ./_build/src/app/bte-2.91
 
 # Or, you can mixup with multiple logging level
-$ VTE_DEBUG=selection,draw,cell ./_build/src/app/bte-2.91
+$ BTE_DEBUG=selection,draw,cell ./_build/src/app/bte-2.91
 
 $ Or, you can use `all` to print out all logging message
-$ VTE_DEBUG=all ./_build/src/app/bte-2.91
+$ BTE_DEBUG=all ./_build/src/app/bte-2.91
 ```
 
 For logging level information, please refer to enum [BteDebugFlags](src/debug.h).

bindings/gir/meson.build

@@ -28,7 +28,7 @@ if get_option('ctk3')
     sources: libbte_ctk3_public_headers + libbte_common_doc_sources,
     includes: libbte_ctk3_gir_includes,
     dependencies: libbte_ctk3_dep,
-    extra_args: '-DVTE_COMPILATION',
+    extra_args: '-DBTE_COMPILATION',
     nsversion: bte_ctk3_api_version,
     namespace: 'Bte',
     export_packages: bte_ctk3_api_name,

bindings/vala/app.vala

@@ -1063,8 +1063,8 @@ class App : Ctk.Application
   {
     Intl.setlocale (LocaleCategory.ALL, "");
 
-    if (Environment.get_variable("VTE_CJK_WIDTH") != null) {
-      printerr("VTE_CJK_WIDTH is not supported anymore, use --cjk-width instead\n");
+    if (Environment.get_variable("BTE_CJK_WIDTH") != null) {
+      printerr("BTE_CJK_WIDTH is not supported anymore, use --cjk-width instead\n");
     }
     /* Not interested in silly debug spew, bug #749195 */
     if (Environment.get_variable("G_ENABLE_DIAGNOSTIC") == null) {
@@ -1074,7 +1074,7 @@ class App : Ctk.Application
     Environment.set_application_name("Terminal");
 
     try {
-      var context = new OptionContext("— simple VTE test application");
+      var context = new OptionContext("— simple BTE test application");
       context.set_help_enabled(true);
       context.add_main_entries(Options.entries, null);
       context.add_group(Ctk.get_option_group(true));
@@ -1085,7 +1085,7 @@ class App : Ctk.Application
     }
 
     if (Options.version) {
-      print("Simple VTE Test Application %s\n", Config.VERSION);
+      print("Simple BTE Test Application %s\n", Config.VERSION);
       return 0;
     }
 

doc/reference/bte-docs.xml

@@ -23,9 +23,9 @@
     -->
 
   <bookinfo>
-    <title>VTE Reference Manual</title>
+    <title>BTE Reference Manual</title>
     <releaseinfo>
-      Documentation for VTE version &version;.
+      Documentation for BTE version &version;.
       The latest version of this documentation can be found on-line at the
       <ulink role="online-location" url="http://library.gnome.org/devel/bte/">GNOME Library</ulink>.
     </releaseinfo>

doc/reference/bte-sections.txt

@@ -114,25 +114,25 @@ bte_terminal_set_clear_background
 bte_terminal_get_color_background_for_draw
 
 <SUBSECTION Standard>
-VTE_TYPE_CURSOR_BLINK_MODE
+BTE_TYPE_CURSOR_BLINK_MODE
 bte_cursor_blink_mode_get_type
-VTE_TYPE_CURSOR_SHAPE
+BTE_TYPE_CURSOR_SHAPE
 bte_cursor_shape_get_type
-VTE_TYPE_ERASE_BINDING
+BTE_TYPE_ERASE_BINDING
 bte_erase_binding_get_type
-VTE_TYPE_TEXT_BLINK_MODE
+BTE_TYPE_TEXT_BLINK_MODE
 bte_text_blink_mode_get_type
-VTE_TYPE_FORMAT
+BTE_TYPE_FORMAT
 bte_format_get_type
-VTE_TYPE_WRITE_FLAGS
+BTE_TYPE_WRITE_FLAGS
 bte_write_flags_get_type
-VTE_TYPE_TERMINAL
+BTE_TYPE_TERMINAL
 bte_terminal_get_type
-VTE_IS_TERMINAL
-VTE_TERMINAL
-VTE_TERMINAL_GET_CLASS
-VTE_IS_TERMINAL_CLASS
-VTE_TERMINAL_CLASS
+BTE_IS_TERMINAL
+BTE_TERMINAL
+BTE_TERMINAL_GET_CLASS
+BTE_IS_TERMINAL_CLASS
+BTE_TERMINAL_CLASS
 
 <SUBSECTION Binding Accessors>
 bte_terminal_get_char_height
@@ -179,9 +179,9 @@ bte_regex_jit
 bte_regex_substitute
 
 <SUBSECTION Standard>
-VTE_TYPE_REGEX
+BTE_TYPE_REGEX
 bte_regex_get_type
-VTE_REGEX_ERROR
+BTE_REGEX_ERROR
 bte_regex_error_quark
 </SECTION>
 
@@ -201,27 +201,27 @@ bte_pty_set_term
 bte_pty_set_utf8
 
 <SUBSECTION>
-VTE_SPAWN_NO_PARENT_ENVV
-VTE_SPAWN_NO_SYSTEMD_SCOPE
-VTE_SPAWN_REQUIRE_SYSTEMD_SCOPE
+BTE_SPAWN_NO_PARENT_ENVV
+BTE_SPAWN_NO_SYSTEMD_SCOPE
+BTE_SPAWN_REQUIRE_SYSTEMD_SCOPE
 bte_pty_spawn_async
 bte_pty_spawn_with_fds_async
 bte_pty_spawn_finish
 
 <SUBSECTION Standard>
 bte_pty_flags_get_type
-VTE_TYPE_PTY_FLAGS
+BTE_TYPE_PTY_FLAGS
 bte_pty_error_get_type
-VTE_TYPE_PTY_ERROR
+BTE_TYPE_PTY_ERROR
 bte_pty_error_quark
-VTE_PTY_ERROR
+BTE_PTY_ERROR
 bte_pty_get_type
-VTE_TYPE_PTY
-VTE_PTY
-VTE_PTY_CLASS
-VTE_IS_PTY
-VTE_IS_PTY_CLASS
-VTE_PTY_GET_CLASS
+BTE_TYPE_PTY
+BTE_PTY
+BTE_PTY_CLASS
+BTE_IS_PTY
+BTE_IS_PTY_CLASS
+BTE_PTY_GET_CLASS
 BtePtyClass
 
 <SUBSECTION Deprecated>
@@ -232,14 +232,14 @@ bte_pty_close
 <FILE>bte-version</FILE>
 <TITLE>Version Information</TITLE>
 
-VTE_MAJOR_VERSION
+BTE_MAJOR_VERSION
 bte_get_major_version
-VTE_MINOR_VERSION
+BTE_MINOR_VERSION
 bte_get_minor_version
-VTE_MICRO_VERSION
+BTE_MICRO_VERSION
 bte_get_micro_version
 
 <SUBSECTION>
-VTE_CHECK_VERSION
+BTE_CHECK_VERSION
 
 </SECTION>

doc/reference/meson.build

@@ -57,8 +57,8 @@ private_headers = [
 ]
 
 scan_args = [
-  '--deprecated-guards="VTE_DISABLE_DEPRECATED"',
-  '--ignore-decorators=_VTE_GNUC_NONNULL\s*\([^)]*\)|_VTE_CXX_NOEXCEPT',
+  '--deprecated-guards="BTE_DISABLE_DEPRECATED"',
+  '--ignore-decorators=_BTE_GNUC_NONNULL\s*\([^)]*\)|_BTE_CXX_NOEXCEPT',
 ]
 
 glib_prefix = glib_dep.get_pkgconfig_variable('prefix')
@@ -92,7 +92,7 @@ if get_option('ctk3')
     ignore_headers: private_headers,
     include_directories: top_inc,
     dependencies: libbte_ctk3_dep,
-    c_args: '-DVTE_COMPILATION',
+    c_args: '-DBTE_COMPILATION',
     namespace: 'bte',
     scan_args: scan_args,
     mkdb_args: '--source-suffixes=h,hh,c,cc',

doc/rewrap.txt

@@ -1,5 +1,5 @@
 ╔════════════════╗
-║ VTE rewrapping ║
+║ BTE rewrapping ║
 ╚════════════════╝
 
 as per the feature request and discussions at
@@ -16,7 +16,7 @@ is resized.
 
 In order to implement this, we need to remember for each line whether we
 advanced to the next because a newline (a.k.a. linefeed) was printed, or
-because the end of line was reached. VTE and most other terminals already
+because the end of line was reached. BTE and most other terminals already
 remember this (even if they don't support rewrap) for copy-paste purposes.
 
 Let's use the following terminology:
@@ -82,11 +82,11 @@ printable character.)
 Other generic expectations
 ──────────────────────────
 
-Window managers can be configured to resize applications (and hence the VTE
+Window managers can be configured to resize applications (and hence the BTE
 widget) only once for the final size, and can resize it continuously. It's
 expected that these two should lead to the same result (as much as possible).
 
-Some terminal emulators scroll to the bottom on resize. VTE has traditionally
+Some terminal emulators scroll to the bottom on resize. BTE has traditionally
 been cleverer, it kept the scroll position. I believe it's a nice feature and
 we should try to keep it the same.
 
@@ -98,7 +98,7 @@ paragraphs were and still are shorter than the width, rewrapping shouldn't
 change the scroll offset. If there was only 1 paragraph that needed to be
 rewrapped from one line to two lines, the content shouldn't scroll by more
 than 1 line anywhere on the screen. If you change the height only, the
-behavior would be the same as with old non-rewrapping VTE. In this case the
+behavior would be the same as with old non-rewrapping BTE. In this case the
 rewrapping code is actually skipped (because it's an expensive operation), but
 even if it was executed, the behavior should remain the same.
 
@@ -118,7 +118,7 @@ The alternate screen should not be rewrapped. It is used by applications that
 have full control over the entire area and they will repaint it themselves.
 Rewrapping by bte would cause ugly artifacts after bte rewraps but before the
 application catches up, e.g. characters aligned below each other would become
-arranged diagonally for a short while. (Moreover, with current VTE design,
+arranged diagonally for a short while. (Moreover, with current BTE design,
 rewrapping the alternate screen would require many new fds to be used: main
 bug comment 60).
 
@@ -189,7 +189,7 @@ Shell prompt
 If you resize the terminal to be narrower than your shell prompt (plus the
 command you're entering) while the shell is waiting for your command, you see
 weird behavior there. This is not a bug in rewrapping: it's because the shell
-redisplays its prompt (and command line) on every resize. There's not much VTE
+redisplays its prompt (and command line) on every resize. There's not much BTE
 could do here.
 
 As a long term goal, maybe readline could have an option where it knows that
@@ -431,7 +431,7 @@ say this is a small glitch we can easily live with.
 Caveats
 ═══════
 
-With extremely large scrollback buffers (let's not forget: VTE supports
+With extremely large scrollback buffers (let's not forget: BTE supports
 infinite scrollback) rewrapping might become slow. On my computer (average
 laptop with Intel(R) Core(TM) i3 CPU, old-fashioned HDD) resizing 1 million
 lines take about 0.2 seconds wall clock time, this is close to the boundary of

meson.build

@@ -119,7 +119,7 @@ config_h = configuration_data()
 
 config_h.set_quoted('GETTEXT_PACKAGE', bte_gettext_domain)
 config_h.set_quoted('VERSION', bte_version)
-config_h.set('VTE_DEBUG', enable_debug)
+config_h.set('BTE_DEBUG', enable_debug)
 config_h.set('WITH_A11Y', get_option('a11y'))
 config_h.set('WITH_FRIBIDI', get_option('fribidi'))
 config_h.set('WITH_GNUTLS', get_option('gnutls'))
@@ -487,7 +487,7 @@ configure_file(
 # Summary
 
 output = '\n'
-output += 'Configuration for VTE:\n\n'
+output += 'Configuration for BTE:\n\n'
 output += '  Version:      ' + bte_version + '\n'
 output += '\n'
 output += '  C compiler:   ' + cc.get_id() + ' (version ' + cc.version() + ')\n'

perf/bidi.sh

@@ -1,4 +1,4 @@
-# BiDi support in VTE is implemented according to
+# BiDi support in BTE is implemented according to
 # https://terminal-wg.pages.freedesktop.org/bidi/
 #
 # The following aliases allow you to quickly change the BiDi mode.

po/es.po

@@ -1,8 +1,8 @@
 # traducción de es.po al Spanish
 # translation of bte.HEAD.po to Spanish
-# VTE Spanish translation file.
+# BTE Spanish translation file.
 # Copyright (C) 2002,2003, 2004, 2007 Free Software Foundation, Inc.
-# This file is distributed under the same license as the VTE package.
+# This file is distributed under the same license as the BTE package.
 #
 # Pablo Gonzalo del Campo <pablodc@bigfoot.com>, 2002.
 # Germán Poo Caamaño <gpoo@ubiobio.cl>, 2002.

po/lv.po

@@ -1,5 +1,5 @@
 # translation of lv.po to Latvian
-# Latvian translation for VTE.
+# Latvian translation for BTE.
 # Copyright © 2006 Gnome i18n Project for Latvian.
 #
 # Artis Trops <hornet@navigator.lv>, 2002.

po/ta.po

@@ -1,5 +1,5 @@
 # translation of bte.HEAD.po to TAMIL
-# Tamil VTE Translation.
+# Tamil BTE Translation.
 # Copyright (C) 2004 Tamil Translation Team
 # This file is distributed under the same license as the PACKAGE package.
 # vivek <vivekananthan_s@rediffmail.com>.

po/vi.po

@@ -1,4 +1,4 @@
-# Vietnamese Translation for VTE.
+# Vietnamese Translation for BTE.
 # Copyright (C) 2002 THE PACKAGE'S COPYRIGHT HOLDER
 # This file is distributed under the same license as the PACKAGE package.
 # T.M.Thanh <tmthanh@yahoo.com>, 2002.