Merge pull request #1611 from horgh/horgh/muon-meson-fmt-workflow

Add muon-meson fmt GitHub Actions workflow

.clang-format

@@ -0,0 +1,38 @@
+# IndentPPDirectives: AfterHash
+# SpaceInParentheses: false
+AlignAfterOpenBracket: Align
+AlignConsecutiveAssignments: false
+AlignConsecutiveDeclarations: false
+AlignOperands: true
+AlignTrailingComments: true
+AllowAllParametersOfDeclarationOnNextLine: true
+AllowShortBlocksOnASingleLine: false
+AllowShortCaseLabelsOnASingleLine: false
+AllowShortFunctionsOnASingleLine: Empty
+AllowShortIfStatementsOnASingleLine: false
+AllowShortLoopsOnASingleLine: false
+AlwaysBreakAfterReturnType: None
+AlwaysBreakBeforeMultilineStrings: false
+BinPackArguments: true
+BinPackParameters: true
+BreakBeforeBinaryOperators: None
+BreakBeforeBraces: Linux
+BreakBeforeTernaryOperators: false
+ColumnLimit: 100
+IndentCaseLabels: false
+IndentWidth: 8
+IndentWrappedFunctionNames: true
+KeepEmptyLinesAtTheStartOfBlocks: false
+Language: Cpp
+Cpp11BracedListStyle: false
+MaxEmptyLinesToKeep: 1
+PointerAlignment: Right
+SortIncludes: false
+SpaceAfterCStyleCast: true
+SpaceBeforeAssignmentOperators: true
+SpaceBeforeParens: ControlStatements
+SpaceInEmptyParentheses: false
+SpacesInCStyleCastParentheses: false
+SpacesInSquareBrackets: false
+TabWidth: 8
+UseTab: ForIndentation

.gitattributes

@@ -0,0 +1,3 @@
+# On Windows, some Git clients may normalize all text files' line-endings to
+# CRLF, which causes obscure errors when running shell scripts.
+*.sh	eol=lf

.github/workflows/abicheck.yml

@@ -0,0 +1,127 @@
+on: [pull_request]
+name: abicheck
+env:
+  build_options: -Dbuildtype=debug -Denable-true-color=yes -Dwith-proxy=yes -Dc_args=-DPERL_EUPXS_ALWAYS_EXPORT
+  prefix: /usr/local
+  apt_build_deps: ninja-build libutf8proc-dev libperl-dev libotr5-dev libglib2.0-dev
+  get_pip_build_deps: pip3 install 'setuptools<66'; pip3 install wheel; pip3 install 'meson<0.59.0'
+  getabidef_def: getabidef() { awk '$1=="#define" && $2=="IRSSI_ABI_VERSION" { print $3 }' "$1"/include/irssi/src/common.h; }
+jobs:
+  build-base-ref:
+    runs-on: ubuntu-latest
+    outputs:
+      base_abi: ${{ steps.out.outputs.base_abi }}
+    steps:
+      - name: set PATH
+        run: |
+          echo "$HOME/.local/bin" >> $GITHUB_PATH
+      - name: prepare required software
+        run: |
+          sudo apt update; sudo apt install $apt_build_deps
+          eval "$get_pip_build_deps"
+      - name: checkout base ref
+        uses: actions/checkout@main
+        with:
+          path: base.src
+          ref: ${{ github.base_ref }}
+      - name: build base ref
+        run: |
+          meson Build.base base.src $build_options
+          ninja -C Build.base
+          DESTDIR=$PWD/base ninja -C Build.base install
+      - id: out
+        run: |
+          # print versions and abi versions
+          eval "$getabidef_def"
+          base_abi=$(getabidef base$prefix)
+          echo base abi : $base_abi
+          ./base$prefix/bin/irssi --version
+          echo base_abi=$base_abi >> $GITHUB_OUTPUT
+      - uses: actions/upload-artifact@v4
+        with:
+          name: base.inst
+          path: base
+          retention-days: 1
+  build-merge-ref:
+    runs-on: ubuntu-latest
+    outputs:
+      merge_abi: ${{ steps.out.outputs.merge_abi }}
+    steps:
+      - name: set PATH
+        run: |
+          echo "$HOME/.local/bin" >> $GITHUB_PATH
+      - name: prepare required software
+        run: |
+          sudo apt update; sudo apt install $apt_build_deps
+          eval "$get_pip_build_deps"
+      - name: checkout merge ref
+        uses: actions/checkout@main
+        with:
+          path: merge.src
+      - name: build merge ref
+        run: |
+          meson Build.merge merge.src $build_options
+          ninja -C Build.merge
+          DESTDIR=$PWD/merge ninja -C Build.merge install
+      - id: out
+        run: |
+          # print versions and abi versions
+          eval "$getabidef_def"
+          merge_abi=$(getabidef merge$prefix)
+          echo merge abi : $merge_abi
+          ./merge$prefix/bin/irssi --version
+          echo merge_abi=$merge_abi >> $GITHUB_OUTPUT
+      - uses: actions/upload-artifact@v4
+        with:
+          name: merge.inst
+          path: merge
+          retention-days: 1
+  check-abi-diff:
+    runs-on: ubuntu-latest
+    needs:
+      - build-merge-ref
+      - build-base-ref
+    env:
+      base_abi: ${{ needs.build-base-ref.outputs.base_abi }}
+      merge_abi: ${{ needs.build-merge-ref.outputs.merge_abi }}
+    steps:
+      - name: prepare required software
+        run: |
+          sudo apt update; sudo apt install abigail-tools
+      - name: fetch base build
+        uses: actions/download-artifact@v4
+        with:
+          name: base.inst
+          path: base
+      - name: fetch merge build
+        uses: actions/download-artifact@v4
+        with:
+          name: merge.inst
+          path: merge
+      - run: |
+          # abipkgdiff
+          abipkgdiff -l base merge >abipkgdiff.out && diff_ret=0 || diff_ret=$?
+          echo "diff_ret=$diff_ret" >> $GITHUB_ENV
+          cat abipkgdiff.out
+      - uses: actions/upload-artifact@v4
+        with:
+          path: abipkgdiff.out
+      - run: |
+          # Check if no changes are needed
+          if [ "$diff_ret" -ne 0 ]; then
+              if [ "$base_abi" -lt "$merge_abi" ]; then
+                  echo "::warning ::abigail found changes and ABI changed from $base_abi to $merge_abi"
+                  exit 0
+              else
+                  echo "::error ::Looks like the ABI changed but the IRSSI_ABI_VERSION did not"
+                  exit $diff_ret
+              fi
+          else
+              if [ "$base_abi" -ne "$merge_abi" ]; then
+                  echo "::error ::abigail found no changes yet the IRSSI_ABI_VERSION changed. Is this correct?"
+                  exit 1
+              else
+                  : "No changes detected and IRSSI_ABI_VERSION untouched"
+                  exit 0
+              fi
+          fi

.github/workflows/check.yml

@@ -0,0 +1,180 @@
+on:
+  push:
+    branches:
+     - master
+  pull_request:
+name: Check Irssi
+env:
+  apt_build_deps: ninja-build libutf8proc-dev libperl-dev libotr5-dev libglib2.0-dev
+  get_pip_build_deps_meson: pip3 install setuptools${setuptools_ver}; pip3 install wheel; pip3 install meson${meson_ver}
+  build_options_meson: -Dwith-proxy=yes -Dwith-bot=yes -Dwith-perl=yes -Dwith-otr=yes
+  prefix: ~/irssi-build
+jobs:
+  dist:
+    runs-on: ubuntu-latest
+    env:
+      meson_ver: <0.63.0
+      setuptools_ver: <66
+    steps:
+      - name: prepare required software
+        run: |
+          sudo apt update && sudo apt install $apt_build_deps
+          eval "$get_pip_build_deps_meson"
+          patch ~/.local/lib/python3.12/site-packages/pkg_resources/__init__.py <<- PATCH
+          --- __init__.py       2024-12-16 20:37:46.733230351 +0100
+          +++ __init__.py       2024-12-16 20:38:42.479554540 +0100
+          @@ -2188,7 +2188,8 @@ def resolve_egg_link(path):
+               return next(dist_groups, ())
+           
+           
+          -register_finder(pkgutil.ImpImporter, find_on_path)
+          +if hasattr(pkgutil, 'ImpImporter'):
+          +    register_finder(pkgutil.ImpImporter, find_on_path)
+           
+           if hasattr(importlib_machinery, 'FileFinder'):
+               register_finder(importlib_machinery.FileFinder, find_on_path)
+          @@ -2345,7 +2346,8 @@ def file_ns_handler(importer, path_item,
+                   return subpath
+           
+           
+          -register_namespace_handler(pkgutil.ImpImporter, file_ns_handler)
+          +if hasattr(pkgutil, 'ImpImporter'):
+          +    register_namespace_handler(pkgutil.ImpImporter, file_ns_handler)
+           register_namespace_handler(zipimport.zipimporter, file_ns_handler)
+           
+           if hasattr(importlib_machinery, 'FileFinder'):
+          PATCH
+      - uses: actions/checkout@main
+      - name: make dist
+        run: |
+          ./utils/make-dist.sh
+      - uses: actions/upload-artifact@v4
+        with:
+          path: irssi-*.tar.gz
+          retention-days: 1
+  install:
+    runs-on: ${{ matrix.os }}
+    env:
+      CC: ${{ matrix.compiler }}
+    needs: dist
+    continue-on-error: ${{ contains(matrix.flags, 'FAILURE-OK') }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-22.04, ubuntu-latest]
+        compiler: [clang, gcc]
+        flags: [regular]
+        setuptools_ver: [<66]
+        include:
+          - os: ubuntu-22.04
+            meson_ver: ==0.53.2
+            setuptools_ver: <51
+          - os: ubuntu-latest
+            meson_ver: <0.63.0
+          - os: ubuntu-latest
+            flags: meson-latest FAILURE-OK
+    steps:
+      - name: fetch dist
+        uses: actions/download-artifact@v4
+      - name: set PATH
+        run: |
+          echo "$HOME/.local/bin" >> $GITHUB_PATH
+      - name: prepare required software
+        env:
+          meson_ver: ${{ matrix.meson_ver }}
+          setuptools_ver: ${{ matrix.setuptools_ver }}
+        run: |
+          sudo apt update && sudo apt install $apt_build_deps
+          eval "$get_pip_build_deps_meson"
+          curl -SLf https://github.com/irssi-import/actions-irssi/raw/master/check-irssi/render.pl -o ~/render.pl && chmod +x ~/render.pl
+      - name: unpack archive
+        run: tar xaf artifact/irssi-*.tar.gz
+      - name: build and install with meson
+        run: |
+          # ninja install
+          cd irssi-*/
+          meson Build $build_options_meson --prefix=${prefix/\~/~}
+          ninja -C Build
+          ninja -C Build install
+      - name: run tests with Meson
+        run: |
+          # ninja test
+          cd irssi-*/
+          ninja -C Build test
+          find -name testlog.txt -exec sed -i -e '/Inherited environment:.* GITHUB/d' {} + -exec cat {} +
+      - name: run launch test
+        env:
+          TERM: xterm
+        run: |
+          # automated irssi launch test
+          cd
+          mkdir irssi-test
+          echo 'echo automated irssi launch test
+          ^set settings_autosave off
+          ^set -clear log_close_string
+          ^set -clear log_day_changed
+          ^set -clear log_open_string
+          ^set log_timestamp * 
+          ^window log on
+          load irc
+          load dcc
+          load flood
+          load notifylist
+          load perl
+          load otr
+          load proxy
+          ^quit' > irssi-test/startup
+          irssi-build/bin/irssi --home irssi-test | perl -Mutf8 -C ~/render.pl
+          cat irc.log.*
+  annotation-warnings:
+    runs-on: ubuntu-latest
+    if: ${{ github.event_name == 'pull_request' }}
+    env:
+      CC: clang
+    steps:
+      - name: prepare required software
+        run: |
+          sudo apt update && sudo apt install $apt_build_deps
+      - uses: actions/checkout@main
+      - name: Setup local annotations
+        uses: irssi-import/actions-irssi/problem-matchers@master
+      - name: set PATH
+        run: |
+          echo "$HOME/.local/bin" >> $GITHUB_PATH
+      - name: prepare required software
+        env:
+          meson_ver: ${{ matrix.meson_ver }}
+          setuptools_ver: ${{ matrix.setuptools_ver }}
+        run: |
+          sudo apt update && sudo apt install $apt_build_deps
+          eval "$get_pip_build_deps_meson"
+          curl -SLf https://github.com/irssi-import/actions-irssi/raw/master/check-irssi/render.pl -o ~/render.pl && chmod +x ~/render.pl
+      - name: build and install with meson
+        run: |
+          meson Build $build_options_meson --prefix=${prefix/\~/~}
+          ninja -C Build
+          ninja -C Build install >/dev/null
+      - name: run launch test
+        env:
+          TERM: xterm
+        run: |
+          # automated irssi launch test
+          cd
+          mkdir irssi-test
+          echo 'echo automated irssi launch test
+          ^set settings_autosave off
+          ^set -clear log_close_string
+          ^set -clear log_day_changed
+          ^set -clear log_open_string
+          ^set log_timestamp * 
+          ^window log on
+          load irc
+          load dcc
+          load flood
+          load notifylist
+          load perl
+          load otr
+          load proxy
+          ^quit' > irssi-test/startup
+          irssi-build/bin/irssi --home irssi-test | perl -Mutf8 -C ~/render.pl
+          cat irc.log.*

.github/workflows/cifuzz.yml

@@ -0,0 +1,51 @@
+name: CIFuzz
+on:
+  pull_request:
+    paths:
+    - 'src/core/**/*.c'
+    - 'src/fe-common/core/**/*.c'
+    - 'src/fe-text/gui-*.c'
+    - 'src/irc/**/*.c'
+    - 'src/fe-common/irc/**/*.c'
+    - 'src/lib-config/**/*.c'
+    - 'src/fe-fuzz/**/*.c'
+    - 'tests/**/*.c'
+    - '.github/workflows/cifuzz.yml'
+jobs:
+  Fuzzing:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        sanitizer: [address, undefined, memory]
+    steps:
+    - uses: actions/checkout@main
+      with:
+        path: irssi
+    - name: Docker build build_fuzzers container
+      run: |
+        # google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
+        docker build -t build_fuzzers:actions -f "/home/runner/work/_actions/google/oss-fuzz/master/infra/build_fuzzers.Dockerfile" "/home/runner/work/_actions/google/oss-fuzz/master/infra"
+    - name: Build Fuzzers (${{ matrix.sanitizer }})
+      id: build
+      env:
+        OSS_FUZZ_PROJECT_NAME: 'irssi'
+        DRY_RUN: false
+        SANITIZER: ${{ matrix.sanitizer }}
+        PROJECT_SRC_PATH: /github/workspace/irssi
+        REPOSITORY: 'irssi'
+      run: |
+        docker run --workdir /github/workspace --rm -e OSS_FUZZ_PROJECT_NAME -e DRY_RUN -e SANITIZER -e PROJECT_SRC_PATH -e REPOSITORY -e WORKSPACE=/github/workspace -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "$GITHUB_WORKSPACE":"/github/workspace" build_fuzzers:actions
+    - name: Run Fuzzers (${{ matrix.sanitizer }})
+      uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
+      with:
+        oss-fuzz-project-name: 'irssi'
+        fuzz-seconds: 600
+        dry-run: false
+        sanitizer: ${{ matrix.sanitizer }}
+    - name: Upload Crash
+      uses: actions/upload-artifact@v4
+      if: failure() && steps.build.outcome == 'success'
+      with:
+        name: ${{ matrix.sanitizer }}-artifacts
+        path: ./out/artifacts

.github/workflows/clangformat.yml

@@ -0,0 +1,29 @@
+on: [pull_request]
+name: clang-format
+jobs:
+  check-clang-format:
+    runs-on: ubuntu-22.04
+    steps:
+      - name: install clang-format
+        run: sudo apt install clang-format-14
+      - uses: actions/checkout@main
+      - name: fetch target ref
+        run:
+          |
+            refs=($(git log -1 --format=%s))
+            git fetch --depth=1 origin "${refs[3]}"
+      - name: configure clang-format
+        run:
+          |
+            git config clangformat.binary $PWD/utils/clang-format-xs/clang-format-xs
+            git config clangformat.extensions c,h,xs
+      - name: run git-clang-format and Check if no changes are needed
+        run:
+          |
+            CLANG_FORMAT=clang-format-14 git-clang-format-14 --diff FETCH_HEAD HEAD | tee git-clang-format.diff
+            cmp -s <(echo no modified files to format) git-clang-format.diff || cmp -s <(echo -n) git-clang-format.diff
+      - uses: actions/upload-artifact@v4
+        if: failure()
+        with:
+          name: git-clang-format.diff
+          path: git-clang-format.diff

.github/workflows/muon-fmt.yml

@@ -0,0 +1,32 @@
+name: Format meson files
+
+on:
+  push:
+  pull_request:
+
+permissions: {}
+
+jobs:
+  muon-meson-fmt:
+    name: Format
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@main
+        with:
+          persist-credentials: false
+
+      # Build from source because Ubuntu 24.04 apt only has muon 0.2.0.
+      # Newer muons seem to format differently.
+      - name: Build muon from source
+        run: |
+          git clone --depth 1 --branch 0.5.0 https://github.com/muon-build/muon /tmp/muon
+          cd /tmp/muon
+          ./bootstrap.sh build
+          build/muon-bootstrap setup build
+          build/muon-bootstrap -C build samu
+          sudo build/muon -C build install
+
+      - name: Run muon fmt
+        run: |
+          find . -name meson.build -print0 | xargs -0 muon fmt -c .muon_fmt.ini -i
+          git diff --exit-code

.github/workflows/solarisvm.yml

@@ -0,0 +1,104 @@
+on:
+  push:
+    branches:
+     - master
+  pull_request:
+  workflow_dispatch:
+name: Check Irssi on Solaris
+env:
+  get_pip_build_deps_meson: pip3 install setuptools${setuptools_ver}; pip3 install wheel
+  prefix: ~/irssi-build
+jobs:
+  dist:
+    runs-on: ubuntu-latest
+    env:
+      setuptools_ver: <66
+    steps:
+      - name: prepare required software
+        run: |
+          sudo apt update && sudo apt install $apt_build_deps
+          eval "$get_pip_build_deps_meson"
+          patch ~/.local/lib/python3.12/site-packages/pkg_resources/__init__.py <<- PATCH
+          --- __init__.py       2024-12-16 20:37:46.733230351 +0100
+          +++ __init__.py       2024-12-16 20:38:42.479554540 +0100
+          @@ -2188,7 +2188,8 @@ def resolve_egg_link(path):
+               return next(dist_groups, ())
+           
+           
+          -register_finder(pkgutil.ImpImporter, find_on_path)
+          +if hasattr(pkgutil, 'ImpImporter'):
+          +    register_finder(pkgutil.ImpImporter, find_on_path)
+           
+           if hasattr(importlib_machinery, 'FileFinder'):
+               register_finder(importlib_machinery.FileFinder, find_on_path)
+          @@ -2345,7 +2346,8 @@ def file_ns_handler(importer, path_item,
+                   return subpath
+           
+           
+          -register_namespace_handler(pkgutil.ImpImporter, file_ns_handler)
+          +if hasattr(pkgutil, 'ImpImporter'):
+          +    register_namespace_handler(pkgutil.ImpImporter, file_ns_handler)
+           register_namespace_handler(zipimport.zipimporter, file_ns_handler)
+           
+           if hasattr(importlib_machinery, 'FileFinder'):
+          PATCH
+      - uses: actions/checkout@main
+      - name: make dist
+        run: |
+          ./utils/make-dist.sh
+      - uses: actions/upload-artifact@v4
+        with:
+          path: irssi-*.tar.gz
+          retention-days: 1
+  install:
+    runs-on: ubuntu-latest
+    needs: dist
+    steps:
+      - name: fetch dist
+        uses: actions/download-artifact@v4
+      - name: Test in Solaris
+        uses: vmactions/solaris-vm@v1
+        with:
+          usesh: true
+          sync: rsync
+          release: "11.4-gcc"
+          prepare: |
+            pkg update --accept || echo 1:$?
+            pkg install meson || echo 2:$?
+            pkgutil -y -i curl || echo 3:$?
+            pkgutil -y -i gtar || echo 4:$?
+            pkgutil -y -i findutils || echo 5:$?
+          run: |
+            set -ex
+            export PKG_CONFIG_PATH=/usr/lib/64/pkgconfig
+            curl -SLf https://github.com/irssi-import/actions-irssi/raw/master/check-irssi/render.pl -o ~/render.pl && chmod +x ~/render.pl
+            gtar xzf artifact/irssi-*.tar.gz
+            # ninja install
+            cd irssi-*/
+            meson Build -Dwith-proxy=yes -Dwith-bot=yes -Dwith-perl=yes --prefix=$HOME/irssi-build
+            ninja -C Build
+            ninja -C Build install
+            # ninja test
+            ninja -C Build test
+            gfind -name testlog.txt -exec gsed -i -e '/Inherited environment:.* GITHUB/d' {} + -exec cat {} +
+            export TERM=xterm
+            # automated irssi launch test
+            cd
+            mkdir irssi-test
+            echo 'echo automated irssi launch test
+            ^set settings_autosave off
+            ^set -clear log_close_string
+            ^set -clear log_day_changed
+            ^set -clear log_open_string
+            ^set log_timestamp * 
+            ^window log on
+            load irc
+            load dcc
+            load flood
+            load notifylist
+            load perl
+            load otr
+            load proxy
+            ^quit' > irssi-test/startup
+            irssi-build/bin/irssi --home irssi-test | perl -Mutf8 -C ~/render.pl
+            cat irc.log.*

.github/workflows/termuxpkg.yml

@@ -0,0 +1,79 @@
+on:
+  push:
+    branches:
+     - master
+  pull_request:
+name: Build Irssi Termux package
+jobs:
+  termux-package:
+    runs-on: ubuntu-latest
+    steps:
+      - name: checkout termux-packages
+        uses: actions/checkout@main
+        with:
+          repository: termux/termux-packages
+      - name: checkout irssi
+        uses: actions/checkout@main
+        with:
+          path: src.irssi.git
+      - name: download termux docker container
+        uses: docker://termux/package-builder:latest
+      - name: create irssi build receipe
+        run: |
+          mkdir packages/irssi-an
+          cat << 'BUILD_SH' > packages/irssi-an/build.sh
+          TERMUX_PKG_HOMEPAGE=https://irssi.org/
+          TERMUX_PKG_DESCRIPTION="Terminal based IRC client"
+          TERMUX_PKG_LICENSE="GPL-2.0"
+          TERMUX_PKG_MAINTAINER="@irssi"
+          TERMUX_PKG_VERSION=@VERSION@
+          TERMUX_PKG_REVISION=@REVISION@
+          TERMUX_PKG_SRCURL=git+file:///home/builder/termux-packages/src.irssi.git
+          TERMUX_PKG_AUTO_UPDATE=true
+          TERMUX_PKG_DEPENDS="glib, libandroid-glob, libiconv, libotr, ncurses, openssl, perl, utf8proc"
+          TERMUX_PKG_BREAKS="irssi"
+          TERMUX_PKG_REPLACES="irssi"
+          TERMUX_MESON_PERL_CROSS_FILE=$TERMUX_PKG_TMPDIR/meson-perl-cross-$TERMUX_ARCH.txt
+          TERMUX_PKG_EXTRA_CONFIGURE_ARGS="
+          -Dfhs-prefix=$TERMUX_PREFIX
+          --cross-file $TERMUX_MESON_PERL_CROSS_FILE
+          "
+
+          termux_step_pre_configure() {
+              LDFLAGS+=" -landroid-glob"
+
+              # Make build log less noisy.
+              CFLAGS+=" -Wno-compound-token-split-by-macro"
+
+              local perl_version=$(. $TERMUX_SCRIPTDIR/packages/perl/build.sh; echo $TERMUX_PKG_VERSION)
+
+              cat << MESON_PERL_CROSS >$TERMUX_MESON_PERL_CROSS_FILE
+          [properties]
+          perl_version = '$perl_version'
+          perl_ccopts = ['-I$TERMUX_PREFIX/include', '-D_LARGEFILE_SOURCE', '-D_FILE_OFFSET_BITS=64', '-I$TERMUX_PREFIX/lib/perl5/$perl_version/${TERMUX_ARCH}-android/CORE']
+          perl_ldopts = ['-Wl,-E', '-I$TERMUX_PREFIX/include', '-L$TERMUX_PREFIX/lib/perl5/$perl_version/${TERMUX_ARCH}-android/CORE', '-lperl', '-lm', '-ldl']
+          perl_archname = '${TERMUX_ARCH}-android'
+          perl_installsitearch = '$TERMUX_PREFIX/lib/perl5/site_perl/$perl_version/${TERMUX_ARCH}-android'
+          perl_installvendorarch = ''
+          perl_inc = ['$TERMUX_PREFIX/lib/perl5/site_perl/$perl_version/${TERMUX_ARCH}-android', '$TERMUX_PREFIX/lib/perl5/site_perl/$perl_version', '$TERMUX_PREFIX/lib/perl5/$perl_version/${TERMUX_ARCH}-android', '$TERMUX_PREFIX/lib/perl5/$perl_version']
+          MESON_PERL_CROSS
+          }
+
+          BUILD_SH
+          version=$(awk '/^v/ { $0=$1; gsub(/^v/,""); gsub(/-head/,"dev"); gsub(/-/,""); print; exit }' src.irssi.git/NEWS)
+          version=$version+g$(git -C src.irssi.git rev-parse --short HEAD)
+          sed -i \
+              -e "s:@VERSION@:$version:" \
+              -e "s:@REVISION@:$GITHUB_RUN_NUMBER:" \
+              packages/irssi-an/build.sh
+          git -C src.irssi.git tag v$version
+      - name: prepare output folder
+        run: |
+          install -m a+rwx -d output
+      - name: build irssi package
+        run: |
+          sudo ./scripts/run-docker.sh ./build-package.sh -I irssi-an
+      - uses: actions/upload-artifact@v4
+        with:
+          name: irssi-termux-pkg
+          path: output/irssi-an*.deb

.github/workflows/trigger-pages.yml

@@ -0,0 +1,20 @@
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  rebuild-pages:
+    if: github.repository == 'irssi/irssi'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/github-script@v6
+        with:
+          github-token: ${{ secrets.PAT_TOKEN }}
+          script: |
+            await github.rest.actions.createWorkflowDispatch({
+              owner: context.repo.owner,
+              repo: 'irssi.github.io',
+              workflow_id: 'pages.yml',
+              ref: 'main'
+            })

.github/workflows/voiddocker.yml

@@ -0,0 +1,75 @@
+on:
+  push:
+    branches:
+     - master
+  pull_request:
+  workflow_dispatch:
+name: Check Irssi on Void Linux glibc
+jobs:
+  dist:
+    runs-on: ubuntu-latest
+    container: ghcr.io/void-linux/void-glibc:latest
+    steps:
+      - name: prepare required software
+        run: |
+          xbps-install -Syu xbps || :
+          xbps-install -Syu
+          xbps-install -Sy git findutils python3-setuptools tar xz gzip
+      - uses: actions/checkout@main
+      - name: make dist
+        run: |
+          git config --global --add safe.directory /__w/irssi/irssi
+          ./utils/make-dist.sh
+      - uses: actions/upload-artifact@v4
+        with:
+          path: irssi-*.tar.gz
+          retention-days: 1
+  install:
+    runs-on: ubuntu-latest
+    container: ghcr.io/void-linux/void-glibc:latest
+    needs: dist
+    steps:
+      - name: prepare required software
+        run: |
+          xbps-install -Syu xbps || :
+          xbps-install -Syu
+          xbps-install -Sy meson base-devel libglib-devel libutf8proc-devel ncurses-devel ncurses-base openssl-devel libotr-devel libgcrypt-devel tar findutils curl
+      - name: fetch dist
+        uses: actions/download-artifact@v4
+      - name: Setup local annotations
+        uses: irssi-import/actions-irssi/problem-matchers@master
+      - name: Test on Void Linux glibc
+        run: |
+          set -ex
+          curl -SLf https://github.com/irssi-import/actions-irssi/raw/master/check-irssi/render.pl -o ~/render.pl && chmod +x ~/render.pl
+          tar xzf artifact/irssi-*.tar.gz
+          # ninja install
+          cd irssi-*/
+          meson Build -Dwith-proxy=yes -Dwith-bot=yes -Dwith-perl=yes --prefix=$HOME/irssi-build --buildtype debugoptimized
+          ninja -C Build
+          ninja -C Build install
+          # ninja test
+          ninja -C Build test
+          find -name testlog.txt -exec sed -i -e '/Inherited environment:.* GITHUB/d' {} + -exec cat {} +
+          export TERM=xterm
+          # automated irssi launch test
+          cd
+          mkdir irssi-test
+          echo 'echo automated irssi launch test
+          ^set settings_autosave off
+          ^set -clear log_close_string
+          ^set -clear log_day_changed
+          ^set -clear log_open_string
+          ^set log_timestamp * 
+          ^window log on
+          load irc
+          load dcc
+          load flood
+          load notifylist
+          load perl
+          load otr
+          load proxy
+          ^quit' > irssi-test/startup
+          export LC_CTYPE=C.utf8
+          irssi-build/bin/irssi --home irssi-test | perl -Mutf8 -C ~/render.pl
+          cat irc.log.*

.gitignore

@@ -0,0 +1,91 @@
+ChangeLog
+Makefile
+Makefile.PL
+Makefile.in
+aclocal.m4
+autom4te.cache
+blib
+build-aux
+config.log
+config.status
+configure
+default-config.h
+default-theme.h
+irssi-config
+irssi-config.h
+irssi-config.h.in
+irssi-version.h
+libtool
+libtool.m4
+ltoptions.m4
+ltsugar.m4
+ltversion.m4
+lt~obsolete.m4
+pm_to_blib
+stamp-h1
+MYMETA.*
+
+docs/help/Makefile.am
+docs/help/[a-z]*
+!docs/help/meson.build
+!docs/help/in
+docs/help/in/Makefile.am
+
+src/fe-text/irssi
+src/fe-fuzz/irssi-fuzz
+src/fe-fuzz/irc/core/event-get-params-fuzz
+src/fe-fuzz/fe-common/core/theme-load-fuzz
+
+src/perl/perl-signals-list.h
+src/perl/irssi-core.pl.h
+
+src/perl/common/*.c
+src/perl/irc/*.c
+src/perl/textui/*.c
+src/perl/ui/*.c
+src/perl/*/MYMETA.*
+src/perl/*/Makefile.old
+
+src/fe-fuzz/crash-*
+src/fe-fuzz/oom-*
+
+/core
+/irssi-1.pc
+/irssi/
+/tests/fe-common/core/test-formats
+/tests/fe-common/core/test-formats.log
+/tests/fe-common/core/test-formats.trs
+/tests/fe-common/core/test-suite.log
+/tests/irc/core/core
+/tests/irc/core/test-channel-events
+/tests/irc/core/test-channel-events.log
+/tests/irc/core/test-channel-events.trs
+/tests/irc/core/test-irc
+/tests/irc/core/test-irc.log
+/tests/irc/core/test-irc.trs
+/tests/irc/core/test-suite.log
+/tests/irc/flood/test-796
+/tests/irc/flood/test-796.log
+/tests/irc/flood/test-796.trs
+/tests/irc/flood/test-suite.log
+
+*.a
+*.bs
+*.la
+*.lo
+*.o
+*.swp
+*~
+
+*.tar.bz2
+*.tar.gz
+
+.deps
+.libs
+
+Build
+subprojects/*
+!subprojects/*.wrap
+Irssi-Dist
+setup.cfg
+*.egg-info

.muon_fmt.ini

@@ -0,0 +1,14 @@
+# Irssi configuration for muon fmt
+max_line_len = 108
+indent_style = space
+indent_size = 2
+#indent_by = '  '
+space_array = true
+kwargs_force_multiline = true
+wide_colon = true
+no_single_comma_function = true
+insert_final_newline = true
+sort_files = false
+group_arg_value = true
+sticky_parens = true
+continuation_indent = true

.obs/workflows.yml

@@ -0,0 +1,13 @@
+workflow:
+  steps:
+    - branch_package:
+        source_project: home:ailin_nemui:irssi-git-an
+        source_package: irssi-git-an
+        target_project: home:ailin_nemui:CI
+    - set_flags:
+        flags:
+          - type: publish
+            status: enable
+            project: home:ailin_nemui:CI
+  filters:
+    event: pull_request

AUTHORS

@@ -10,6 +10,10 @@ Irssi staff (current maintainers) <staff@irssi.org>:
   Geert Hauwaerts (Geert)
   Jilles Tjoelker (jilles)
   Alexander Færøy (ahf)
+  Jase Thew (bazerka)
+  dequis (dx)
+  Ailin Nemui (Nei)
+  Giuseppe (TheLemonMan, lemonboy)
 
 Former developers:
 
@@ -23,6 +27,8 @@ Large feature patches by:
   Heikki Orsila : DCC SEND queueing
   Mark Trumbull : DCC SERVER
   Francesco Fracassi : Passive DCC
+  Uli Meis : OTR support
+  David Goulet : OTR support
 
 Other patches (grep for "patch" in ChangeLog) by:
 
@@ -73,6 +79,25 @@ Other patches (grep for "patch" in ChangeLog) by:
   Jon Mayo
   Johan Kiviniemi
   JasonX
-  Lukas Mai
+  Lukas Mai (mauke)
   Ismael Luceno
   Thomas Karpiniec
+  Svante Kvarnström
+  Tom Feist (shabble)
+  Sebastian Thorarensen (Sebban)
+  Hans Nielsen
+  Jari Matilainen (vague)
+  Thibault B (isundil)
+  kyak
+  Vesa Pirila (Lohhari)
+  Haw Loeung
+  François Revol (mmuman)
+  blha303
+  Guillaume Brogi (guiniol)
+  Adam-
+  Robert C Jensen
+  Paul Johnson
+  KindOne
+  Fabian Kurz
+  Todd Pratt
+  xavierog

INSTALL

@@ -2,77 +2,68 @@
  Irssi installation instructions
  -------------------------------
 
-To compile irssi you need:
+To compile Irssi you need:
 
-- glib-2.6 or greater
-- pkg-config
+- meson-0.53 build system with ninja-1.8 or greater
+- pkg-config (or compatible)
+- glib-2.32 or greater
 - openssl (for ssl support)
-- perl-5.6 or greater (for perl support)
+- perl-5.8 or greater (for building, and optionally Perl scripts)
+  (n.b a complete perl is needed, including ExtUtils::Embed and xsubpp)
+- terminfo or ncurses (for text frontend)
+- utf8proc (optional, for additional char width calculation)
+- libgcrypt (for OTR)
 
 For most people, this should work just fine:
 
- ./configure
- make
+ meson Build
+ ninja -C Build
  su
- make install     (not _really_ required except for perl support)
+ ninja -C Build install
+ 
+meson options
 
-configure options
+  These options can be given to meson.
+  
+  For a complete list of options, run
+   meson configure
 
   --prefix
 
-  Specifies the path where irssi will be installed.
-  YES, you can install irssi WITHOUT ROOT permissions
+  Specifies the path where Irssi will be installed.
+  YES, you can install Irssi WITHOUT ROOT permissions
   by using --prefix=/home/dir
 
-  --with-proxy
+  -Dwith-proxy=yes
 
-  Build the irssi proxy (see startup-HOWTO).
+  Build the Irssi proxy (see startup-HOWTO).
 
-  --disable-ipv6
-
-  Disable IPv6 support.
-
-  --disable-ssl
-
-  Disable SSL support.
-
-  --with-perl=[yes|no|module]
+  -Dwith-perl=[yes|no]
 
   Enable Perl support
   yes    enable builtin (default)
   no     disable
-  module enable as module
 
-  --with-perl-lib=[site|vendor|DIR]
+  -Dwith-perl-lib=[site|vendor|DIR]
 
   Specify installation dir for Perl libraries
   site   install in dir for site-specific modules (default)
   vendor install in dir for vendor-specific modules
   DIR    install in DIR
 
-  --with-socks
-
-  Build with socks library
-
-  --with-bot
+  -Dwith-bot=yes
 
   Build irssi-bot
 
-  --without-textui
+  -Dwithout-textui=yes
 
   Build without text frontend
 
-If ncurses is installed in a non-standard path you can specify it with
---with-ncurses=/path. If anything else is in non-standard path, you can just
-give the paths in CPPFLAGS and LIBS environment variable, eg.:
+If anything is in non-standard path, you can just give the paths in
+the -Dc_args and -Dc_link_args options variable, eg.:
 
-  CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib ./configure
+  meson Build -Dc_args='-I/opt/openssl/include' -Dc_link_args='-L/opt/openssl/lib'
 
-Irssi doesn't really need curses anymore, by default it uses
-terminfo/termcap directly. The functions for using terminfo/termcap
-however are usually only in curses library, some systems use libtermcap
-as well. If you want to use only curses calls for some reason, use
---without-terminfo.
 
 
  Perl problems
@@ -81,17 +72,9 @@ as well. If you want to use only curses calls for some reason, use
 Perl support generates most of the problems. There's quite a many
 things that can go wrong:
 
- - Compiling fails if you compile irssi with GCC in a system that has
-   perl compiled with some other C compiler. Very common problem with
-   non-Linux/BSD systems. You'll need to edit src/perl/*/Makefile files
-   and remove the parameters that gcc doesn't like. Mostly you'll just
-   need to keep the -I and -D parameters and add -fPIC.
  - If there's any weird crashing at startup, you might have older irssi's
    perl libraries installed somewhere, and you should remove those.
- - Dynamic libraries don't want to work with some systems, so if your
-   system complains about some missing symbol in Irssi.so file, configure
-   irssi with --with-perl-staticlib option (NOT same as --with-perl=static).
- - If configure complains that it doesn't find some perl stuff, you're
+ - If meson complains that it doesn't find some perl stuff, you're
    probably missing libperl.so or libperl.a. In debian, you'll need to do
    apt-get install libperl-dev
 
@@ -100,23 +83,40 @@ command. It should print something like:
 
 Module               Type    Submodules
 ...
-perl                 static  core fe
+perl                 dynamic fe core
 
 
  System specific notes
  ---------------------
 
+ Android
+
+When cross compiling Irssi for Android, you can specify the path of
+the cross-perl in the cross file.
+
+You may not have a cross-perl available. In that case, you will have
+to manually supply the required Perl arguments in the cross file. See
+the commented properties in the example cross file.
+
+An example cross file can be found in the docs folder. To use it, you
+would call:
+
+  meson Build --cross-file cross-android-aarch64.txt \
+    --prefix /data/data/com.termux/files/usr \
+    --libdir lib \
+    -Dfhs-prefix=/data/data/com.termux/files/usr \
+
+
  Cygwin
 
 Getting perl scripting to work needs a few things:
 
- - configure with --with-perl-staticlib
+ - TODO
 
- - libperl.dll is required in linking and running irssi, it's normally
-   located somewhere around /usr/lib/perl5/5.6.1/cygwin/CORE/libperl5_6_1.dll
-   copy it to eg. /usr/bin/libperl.dll
 
- - -DUSEIMPORTLIB is needed to be defined while compiling src/perl directory.
-   It doesn't hurt to be defined everywhere, so configure irssi with:
+ Apple MacOS / Darwin
 
-     CFLAGS='-DUSEIMPORTLIB' ./configure --with-perl-staticlib
+At the time of writing, meson has an open issue with correctly linking
+libraries on macos.
+
+See docs/meson-macos-ar.txt for a workaround.

MANIFEST.in

@@ -0,0 +1,35 @@
+global-include meson.build
+
+recursive-include src *.c *.h meson.build
+recursive-include src/perl *.c *.h *.xs *.pm *.pl typemap meson.build
+recursive-include src/fe-fuzz *.c *.h *.txt meson.build
+recursive-include tests *.c meson.build
+
+include meson_options.txt
+
+include subprojects/*.wrap
+# prune subprojects/*
+
+include utils/*.pl utils/*.sh
+exclude utils/make-dist.sh
+
+include irssi.conf
+include themes/*.theme
+include docs/*.1 docs/*.txt docs/*.html
+include docs/help/in/[a-z]*.in
+include scripts/*.pl scripts/examples/*.pl
+include irssi-icon.png
+
+include NEWS
+include INSTALL
+include TODO
+include ChangeLog
+
+include .clang-format
+
+# prune Build
+# prune dist
+prune *.egg-info
+
+# ignore fuzz-support/fuzz.diff
+# ignore utils/clang-format-xs/*

Makefile.am

@@ -1,36 +0,0 @@
-ACLOCAL_AMFLAGS = -I .
-
-# create default-config.h
-BUILT_SOURCES = default-config.h default-theme.h irssi-version.h
-
-.PHONY: irssi-version.h
-
-default-config.h: $(srcdir)/irssi.conf
-	$(srcdir)/file2header.sh $(srcdir)/irssi.conf default_config > default-config.h
-default-theme.h: $(srcdir)/default.theme
-	$(srcdir)/file2header.sh $(srcdir)/default.theme default_theme > default-theme.h
-irssi-version.h:
-	$(srcdir)/irssi-version.sh $(srcdir) | cmp -s - $@ || $(srcdir)/irssi-version.sh $(srcdir) >$@
-
-SUBDIRS = src docs scripts
-
-confdir = $(sysconfdir)
-conf_DATA = irssi.conf
-
-themedir = $(datadir)/irssi/themes
-theme_DATA = default.theme colorless.theme
-
-pkginclude_HEADERS = irssi-config.h irssi-version.h
-
-EXTRA_DIST = \
-	ChangeLog \
-	autogen.sh \
-	curses.m4 \
-	README \
-	file2header.sh \
-	$(conf_DATA) \
-	$(theme_DATA) \
-	irssi-config.in \
-	irssi-icon.png \
-	irssi-version.sh \
-	syntax.pl

README

@@ -1,115 +0,0 @@
-
-
-irssi, http://irssi.org
-
-
- * INSTALLATION
-
-See INSTALL file.
-
-
- * FILES
-
- - docs/ directory contains several documents:
-    - startup-HOWTO.txt - new users should read this
-    - manual.txt - manual I started writing but didn't get it very far :)
-    - perl.txt - Perl scripting help
-    - formats.txt - How to use colors, etc. with irssi
-    - faq.txt - Frequently Asked Questions
-    - special_vars.txt - some predefined $variables you can use with irssi
-
-
- * ABOUT
-
-Irssi is a modular IRC client that currently has only text mode user
-interface, but 80-90% of the code isn't text mode specific, so other
-UIs could be created pretty easily. Also, Irssi isn't really even IRC
-specific anymore, there's already a working SILC (http://www.silcnet.org)
-module available. Support for other protocols like ICQ could be created
-some day too.
-
-
- * FEATURES
-
-So what's so great about Irssi? Here's a list of some features I can
-think of currently:
-
- - Optional automation - There's lots of things Irssi does for you
-   automatically that some people like and others just hate. Things like:
-   nick completion, creating new window for newly joined channel, creating
-   queries when msgs/notices are received or when you send a msg, closing
-   queries when it's been idle for some time, etc.
-
- - Multiserver friendy - I think Irssi has clearly the best support
-   for handling multiple server connections. You can have as many as you
-   want in as many ircnets as you want. Having several connections in one
-   server works too, for example when you hit the (ircnet's) 10
-   channels/connection limit you can just create another connection and
-   you hardly notice it. If connection to server is lost, Irssi tries to
-   connect back until it's successful. Also channels you were joined
-   before disconnection are restored, even if they're "temporarily
-   unavailable" because of netsplits, Irssi keeps rejoining back to them.
-   Also worth noticing - there's not that stupid "server is bound to this
-   window, if this window gets closed the connection closes" thing that
-   ircII based clients have.
-
- - Channel automation - You can specify what channels to join to
-   immediately after connected to some server or IRC network. After joined
-   to channel, Irssi can automatically request ops for you (or do
-   anything, actually) from channel's bots.
-
- - Window content saving - Say /LAYOUT SAVE when you've put all the
-   channels and queries to their correct place, and after restarting
-   Irssi, the channels will be joined back into windows where they were
-   saved.
-
- - Tab completing anything - You can complete lots of things with tab:
-   nicks, commands, command -options, file names, settings, text format
-   names, channels and server names. There's also an excellent /msg
-   completion that works transparently with multiple IRC networks.
-   Completing channel nicks is also pretty intelligent, it first goes
-   through the people who have talked to you recently, then the people who
-   have talked to anyone recently and only then it fallbacks to rest of
-   the nicks. You can also complete a set of words you've specified, for
-   example homepage<tab> changes it to your actual home page URL.
-
- - Excellent logging - You can log any way you want and as easily or
-   hard as you want. With autologging Irssi logs everything to specified
-   directory, one file per channel/nick. ircII style /WINDOW LOG ON is
-   also supported. There's also the "hard way" of logging - /LOG command
-   which lets you specify exactly what you wish to log and where. Log
-   rotating is supported with all the different logging methods, you can
-   specify how often you want it to rotate and what kind of time stamp to
-   use.
-
- - Excellent ignoring - You can most probably ignore anything any way
-   you want. Nick masks, words, regular expressions. You can add
-   exceptions to ignores. You can ignore other people's replies in
-   channels to nicks you have ignored. You can also specify that the
-   specific ignores work only in specific channel(s).
-
- - Lastlog and scrollback handling - /LASTLOG command has some new
-   features: -new option checks only lines that came since you last did
-   /LASTLOG command, -away option checks new lines since you last went
-   away. Regular expression matches work also, of course. Going to some
-   wanted place at scrollback has always been hard with non-GUI clients. A
-   search command that jumps around in scrollback in GUI-style is still
-   missing from Irssi, but there's something that's almost as good as it.
-   /LASTLOG always shows timestamps when the line was printed, even if you
-   didn't have timestamps on. Now doing /SB GOTO <timestamp> jumps
-   directly to the position in scrollback you wanted. Great feature when
-   you want to browse a bit of the discussion what happened when someone
-   said your name (as seen in awaylog) or topic was changed (/last
-   -topics)
-
-
- * BUGS / SUGGESTIONS
-
-See TODO file and http://bugs.irssi.org if it is already listed in there;
-if not open a bugreport on http://bugs.irssi.org or send a mail to
-staff@irssi.org
-
-You can also contact the Irssi developers on #irssi @ EFnet, Freenode, IRCnet,
-Quakenet and Undernet.
-
-The IRCnet channel is for development related questions and discussions.

README.md

@@ -0,0 +1,74 @@
+# [Irssi](https://irssi.org)
+
+![Build Status](https://github.com/irssi/irssi/workflows/Check%20Irssi/badge.svg?branch=master)
+
+Irssi is a modular text mode chat client. It comes with IRC support
+built in, and there are third party
+[ICB](https://github.com/jperkin/irssi-icb),
+[SILC](http://www.silcnet.org/),
+[XMPP](http://cybione.org/~irssi-xmpp/) (Jabber),
+[PSYC](http://about.psyc.eu/Irssyc) and
+[Quassel](https://github.com/phhusson/quassel-irssi) protocol modules
+available.
+
+![irssi](https://user-images.githubusercontent.com/5665186/32180643-cf127f60-bd92-11e7-8aa2-882313ce1d8e.png)
+
+## [Download information](https://irssi.org/download/)
+
+#### Development source installation
+
+[Ninja](https://ninja-build.org/) 1.8 and [Meson](https://mesonbuild.com/) 0.53
+
+```
+git clone https://github.com/irssi/irssi
+cd irssi
+meson Build
+ninja -C Build && sudo ninja -C Build install
+```
+
+#### Release source installation
+
+* Download [release](https://github.com/irssi/irssi/releases)
+* Verify signature
+```
+tar xJf irssi-*.tar.xz
+cd irssi-*
+meson Build
+ninja -C Build && sudo ninja -C Build install
+```
+
+### Requirements
+
+- [glib-2.32](https://wiki.gnome.org/Projects/GLib) or greater
+- [openssl](https://www.openssl.org/)
+- [perl-5.8](https://www.perl.org/) or greater (for perl support)
+- terminfo or ncurses (for text frontend)
+
+#### See the [INSTALL](INSTALL) file for details
+
+## [Documentation](https://irssi.org/documentation/)
+
+* [New users guide](https://irssi.org/New-users/)
+* [Questions and Answers](https://irssi.org/documentation/qna/)
+* Check the built-in `/HELP`, it has all the details on command syntax
+
+## [Themes](https://irssi-import.github.io/themes/)
+
+## [Scripts](https://scripts.irssi.org/)
+
+## [Modules](https://irssi.org/modules/)
+
+## [Security information](https://irssi.org/security/)
+
+Please report security issues to staff@irssi.org. Thanks!
+
+## [Bugs](https://github.com/irssi/irssi/issues) / Suggestions / Contributing
+
+Check the GitHub issues if it is already listed in there; if not, open
+an issue on GitHub or send a mail to [staff@irssi.org](mailto:staff@irssi.org).
+
+Irssi is always looking for developers. Feel free to submit patches through
+GitHub pull requests.
+
+You can also contact the Irssi developers in
+[#irssi](https://irssi.org/support/irc/) on irc.libera.chat.

acconfig.h

@@ -1,34 +0,0 @@
-/* misc.. */
-#undef HAVE_IPV6
-#undef HAVE_SOCKS_H
-#undef HAVE_STATIC_PERL
-#undef HAVE_GMODULE
-#undef HAVE_GC_H
-#undef HAVE_GC_GC_H
-#undef USE_GC
-
-/* macros/curses checks */
-#undef HAS_CURSES
-#undef USE_SUNOS_CURSES
-#undef USE_BSD_CURSES
-#undef USE_SYSV_CURSES
-#undef USE_NCURSES
-#undef NO_COLOR_CURSES
-#undef SCO_FLAVOR
-
-/* our own curses checks */
-#undef HAVE_NCURSES_USE_DEFAULT_COLORS
-#undef HAVE_CURSES_IDCOK
-#undef HAVE_CURSES_RESIZETERM
-#undef HAVE_CURSES_WRESIZE
-
-/* terminfo/termcap */
-#undef HAVE_TERMINFO
-
-/* What type should be used for uoff_t */
-#undef UOFF_T_INT
-#undef UOFF_T_LONG
-#undef UOFF_T_LONG_LONG
-
-/* printf()-format for uoff_t, eg. "u" or "lu" or "llu" */
-#undef PRIuUOFF_T

autogen.sh

@@ -1,70 +0,0 @@
-#!/bin/sh
-# Run this to generate all the initial makefiles, etc.
-
-PKG_NAME="Irssi"
-
-srcdir=`dirname $0`
-test -z "$srcdir" && srcdir=.
-
-if test ! -f $srcdir/irssi.cvs -a -f $srcdir/configure; then
-  echo
-  echo "Use ./configure instead"
-  echo
-  echo "This script should only be run if you got sources from SVN."
-  echo "If you really want to do this, say:"
-  echo "  touch irssi.cvs"
-  exit 0
-fi
-
-if test ! -f $srcdir/configure.in; then
-    echo -n "**Error**: Directory \`$srcdir\' does not look like the"
-    echo " top-level $PKG_NAME directory"
-    exit 1
-fi
-
-# create help files
-echo "Creating help files..."
-perl syntax.pl
-
-$srcdir/update-changelog.sh $srcdir
-
-files=`echo docs/help/in/*.in|sed -e 's,docs/help/in/Makefile.in ,,' -e 's,docs/help/in/,!,g' -e 's/\.in /.in ?/g'`
-cat docs/help/in/Makefile.am.gen|sed "s/@HELPFILES@/$files/g"|sed 's/?/\\?/g'|tr '!?' '\t\n' > docs/help/in/Makefile.am
-
-files=`echo $files|sed 's/\.in//g'`
-cat docs/help/Makefile.am.gen|sed "s/@HELPFILES@/$files/g"|sed 's/?/\\?/g'|tr '!?' '\t\n' > docs/help/Makefile.am
-
-# .html -> .txt with lynx or elinks
-echo "Documentation: html -> txt..."
-if type lynx >/dev/null 2>&1 ; then
-  lynx -dump -nolist docs/faq.html|perl -pe 's/^ *//; if ($_ eq "\n" && $state eq "Q") { $_ = ""; } elsif (/^([QA]):/) { $state = $1 } elsif ($_ ne "\n") { $_ = "   $_"; };' > docs/faq.txt
-elif type elinks >/dev/null 2>&1 ; then
-  elinks -dump docs/faq.html|perl -pe 's/^ *//; if ($_ eq "\n" && $state eq "Q") { $_ = ""; } elsif (/^([QA]):/) { $state = $1 } elsif ($_ ne "\n") { $_ = "   $_"; };' > docs/faq.txt
-else
-  echo "**Error**: No lynx or links present"
-  exit 1
-fi
-
-if test x$NOCONFIGURE = x && test -z "$*"; then
-  echo "**Warning**: I am going to run \`configure' with no arguments."
-  echo "If you wish to pass any to it, please specify them on the"
-  echo \`$0\'" command line."
-  echo
-fi
-
-rm -f aclocal.m4
-echo "Running autoreconf ..."
-autoreconf -i || exit 1
-
-conf_flags="--enable-maintainer-mode"
-
-if test x$NOCONFIGURE = x; then
-  echo Running $srcdir/configure $conf_flags "$@" ...
-  $srcdir/configure $conf_flags "$@" \
-  && echo Now type \`make\' to compile $PKG_NAME || exit 1
-else
-  echo Skipping configure process.
-fi
-
-# make sure perl hashes have correct length
-find src/perl -name *.c -o -name *.xs | xargs grep -n hv_store | perl -ne 'if (/"(\w+)",\s*(\d+)/) { print unless $2 == length $1 }'

configure.in

@@ -1,738 +0,0 @@
-AC_INIT(irssi, 0.8.15)
-AC_CONFIG_SRCDIR([src])
-AC_CONFIG_AUX_DIR(build-aux)
-AC_PREREQ(2.50)
-
-AC_CONFIG_HEADERS([irssi-config.h])
-AM_INIT_AUTOMAKE([1.9 no-define foreign])
-
-AM_MAINTAINER_MODE
-
-AC_ISC_POSIX
-AC_PROG_CC
-AC_PROG_CPP
-AM_PROG_LIBTOOL
-
-AC_PATH_PROG(sedpath, sed)
-AC_PATH_PROG(perlpath, perl)
-
-AC_CHECK_HEADERS(unistd.h dirent.h sys/ioctl.h sys/resource.h)
-
-# check posix headers..
-AC_CHECK_HEADERS(sys/time.h sys/utsname.h regex.h)
-
-AC_SYS_LARGEFILE
-
-AC_ARG_WITH(socks,
-[  --with-socks            Build with socks support],
-	if test x$withval = xno; then
-		want_socks=no
-	else
-		want_socks=yes
-	fi,
-	want_socks=no)
-
-AC_ARG_WITH(textui,
-[  --without-textui        Build without text frontend],
-	if test x$withval = xno; then
-		want_textui=no
-	else
-		want_textui=yes
-	fi,
-	want_textui=yes)
-
-AC_ARG_WITH(bot,
-[  --with-bot              Build irssi-bot],
-	if test x$withval = xno; then
-		want_irssibot=no
-	else
-		want_irssibot=yes
-	fi,
-	want_irssibot=no)
-
-AC_ARG_WITH(proxy,
-[  --with-proxy            Build irssi-proxy],
-	if test x$withval = xno; then
-		want_irssiproxy=no
-	else
-		want_irssiproxy=yes
-	fi,
-	want_irssiproxy=no)
-
-AC_ARG_WITH(terminfo,
-[  --without-terminfo      Use curses backend instead of terminfo],
-	if test x$withval = xno; then
-		want_terminfo=no
-	else
-		want_terminfo=yes
-	fi,
-	want_terminfo=yes)
-
-AC_ARG_WITH(modules,
-[  --with-modules          Specify what modules to build in binary],
-	if test x$withval != xyes -a x$withval != xno; then
-		build_modules="$withval"
-	fi)
-
-if test "x$prefix" != "xNONE"; then
-	prefix=`eval echo $prefix`
-	PERL_MM_PARAMS="INSTALLDIRS=perl PREFIX=$prefix"
-	perl_library_dir="PERL_USE_LIB"
-	perl_set_use_lib=yes
-
-	perl_prefix_note=yes
-fi
-
-AC_ARG_WITH(gc,
-[  --with-gc               Use garbage collector],
-	if test x$withval = xno; then
-		want_gc=no
-	else
-		want_gc=yes
-	fi,
-	want_gc=no)
-
-AC_ARG_WITH(perl-staticlib,
-[  --with-perl-staticlib   Specify that we want to link perl libraries
-                          statically in irssi, default is no],
-	if test x$withval = xno; then
-		want_staticperllib=no
-	else
-		want_staticperllib=yes
-	fi,
-	want_staticperllib=no)
-
-
-AC_ARG_WITH(perl-lib,
-[  --with-perl-lib=[site|vendor|DIR]  Specify where to install the
-                          Perl libraries for irssi, default is site],
-	if test "x$withval" = xyes; then
-		want_perl=yes
-	elif test "x$withval" = xno; then
-		want_perl=no
-	elif test "x$withval" = xsite; then
-		want_perl=yes
-		perl_prefix_note=no
-		PERL_MM_PARAMS=""
-	elif test "x$withval" = xvendor; then
-		want_perl=yes
-		perl_prefix_note=no
-		if test -z "`$perlpath -v|grep '5\.0'`"; then
-			PERL_MM_PARAMS="INSTALLDIRS=vendor"
-		else
-			PERL_MM_PARAMS="INSTALLDIRS=perl PREFIX=`perl -e 'use Config; print $Config{prefix}'`"
-		fi
-		perl_library_dir="(vendor default - `$perlpath -e 'use Config; print $Config{archlib}'`)"
-	else
-		want_perl=yes
-		perl_prefix_note=no
-		PERL_MM_PARAMS="INSTALLDIRS=perl LIB=$withval"
-		perl_library_dir="PERL_USE_LIB"
-		perl_set_use_lib=yes
-	fi,
-	want_perl=yes)
-
-AC_ARG_WITH(perl,
-[  --with-perl[=yes|no|module]  Build with Perl support - also specifies
-                          if it should be built into main irssi binary
-                          (static, default) or as module],
-	if test x$withval = xyes; then
-		want_perl=static
-	elif test x$withval = xstatic; then
-		want_perl=static
-	elif test x$withval = xmodule; then
-		want_perl=module
-	else
-		want_perl=no
-	fi,
-	want_perl=static)
-
-AC_ARG_ENABLE(ipv6,
-[  --disable-ipv6          Disable IPv6 support],
-	if test x$enableval = xno; then
-		want_ipv6=no
-	else
-		want_ipv6=yes
-	fi,
-	want_ipv6=yes)
-
-dnl **
-dnl ** SSL Library checks (OpenSSL)
-dnl **
-
-AC_ARG_ENABLE(ssl,
-[  --disable-ssl           Disable Secure Sockets Layer support],,
-	enable_ssl=yes)
-
-dnl **
-dnl ** just some generic stuff...
-dnl **
-
-dnl * OS specific options
-case "$host_os" in
-  hpux*)
-    CFLAGS="$CFLAGS -D_XOPEN_SOURCE_EXTENDED"
-    ;;
-  *)
-    ;;
-esac
-
-
-AC_CHECK_FUNC(socket, [], [
-	AC_CHECK_LIB(socket, socket, [
-		LIBS="$LIBS -lsocket"
-	])
-])
-
-AC_CHECK_FUNC(inet_addr, [], [
-	AC_CHECK_LIB(nsl, inet_addr, [
-		LIBS="$LIBS -lnsl"
-	])
-])
-
-dnl * gcc specific options
-if test "x$ac_cv_prog_gcc" = "xyes"; then
-  CFLAGS="$CFLAGS -Wall"
-fi
-
-dnl * socklen_t - AC_CHECK_TYPE() would be _really_ useful if it only would
-dnl * accept header files where to find the typedef..
-AC_MSG_CHECKING([for socklen_t])
-AC_CACHE_VAL(irssi_cv_type_socklen_t,
-[AC_TRY_COMPILE([
-#include <sys/types.h>
-#include <sys/socket.h>],
-[socklen_t t;],
-irssi_cv_type_socklen_t=yes,
-irssi_cv_type_socklen_t=no,
-)])
-if test $irssi_cv_type_socklen_t = no; then
-AC_DEFINE(socklen_t, int, Define to 'int' if <sys/socket.h> doesn't define.)
-fi
-AC_MSG_RESULT($irssi_cv_type_socklen_t)
-
-AC_CHECK_SIZEOF(int)
-AC_CHECK_SIZEOF(long)
-AC_CHECK_SIZEOF(long long)
-AC_CHECK_SIZEOF(off_t)
-
-if test $ac_cv_sizeof_off_t = 8; then
-  offt_64bit=yes
-else
-  offt_64bit=no
-fi
-
-if test x$ac_cv_sizeof_off_t = x$ac_cv_sizeof_long; then
-  # try to use unsigned long always first
-  AC_DEFINE_UNQUOTED(PRIuUOFF_T, "lu")
-  AC_DEFINE(UOFF_T_LONG)
-elif test x$ac_cv_sizeof_off_t = x$ac_cv_sizeof_int; then
-  # next try int
-  AC_DEFINE_UNQUOTED(PRIuUOFF_T, "u")
-  AC_DEFINE(UOFF_T_INT)
-elif test x$ac_cv_sizeof_off_t = x$ac_cv_sizeof_long_long; then
-  # and finally long long
-  AC_DEFINE_UNQUOTED(PRIuUOFF_T, "llu")
-  AC_DEFINE(UOFF_T_LONG_LONG)
-else
-  AC_ERROR([Couldn't find integer type for off_t])
-fi
-
-dnl **
-dnl ** check for socks
-dnl **
-
-if test "x$want_socks" = "xyes"; then
-	AC_CHECK_LIB(socks, connect, [
-		AC_DEFINE(HAVE_SOCKS,, Build with socks support)
-		LIBS="$LIBS -lsocks"
-		AC_CHECK_HEADER(socks.h, [
-			AC_DEFINE(HAVE_SOCKS_H)
-			CFLAGS="$CFLAGS -DSOCKS"
-			AC_MSG_RESULT(["socks5 library found, building with it"])
-		], [
-			AC_MSG_RESULT(["socks4 library found, building with it"])
-			CFLAGS="$CFLAGS -Dconnect=Rconnect -Dgetsockname=Rgetsockname -Dgetpeername=Rgetpeername -Dbind=Rbind -Daccept=Raccept -Dlisten=Rlisten -Dselect=Rselect"
-		])
-	])
-fi
-
-dnl **
-dnl ** fe-text checks
-dnl **
-
-for try in 1 2; do
-  if test $try = 1; then
-    glib_modules=gmodule
-  else
-    echo "*** trying without -lgmodule"
-    glib_modules=
-  fi
-  AM_PATH_GLIB_2_0(2.6.0,,, $glib_modules)
-  if test "$GLIB_LIBS"; then
-    if test $glib_modules = gmodule; then
-      AC_DEFINE(HAVE_GMODULE)
-      have_gmodule=yes
-    fi
-    break
-  fi
-done
-
-if test -z "$GLIB_LIBS"; then
-  echo
-  echo "*** If you don't have GLIB, you can get it from ftp://ftp.gtk.org/pub/glib/"
-  echo "*** We recommend you get the latest stable GLIB 2 version."
-  echo "*** Compile and install it, and make sure pkg-config finds it,"
-  echo "*** by adding the path where the .pc file is located to PKG_CONFIG_PATH"
-  echo
-
-  AC_ERROR([GLIB is required to build irssi.])
-fi
-
-LIBS="$LIBS $GLIB_LIBS"
-
-have_openssl=no
-if test "$enable_ssl" = "yes"; then
-  PKG_CHECK_MODULES(SSL, openssl, :, :)
-  if test "$SSL_LIBS"; then
-    CFLAGS="$CFLAGS $SSL_CFLAGS"
-    have_openssl=yes
-  else
-    AC_CHECK_LIB(ssl, SSL_read, [
-      AC_CHECK_HEADERS(openssl/ssl.h openssl/err.h, [
-	SSL_LIBS="-lssl -lcrypto"
-	have_openssl=yes
-      ])
-    ],, -lcrypto)
-  fi
-  if test "$have_openssl" = "yes"; then
-    AC_DEFINE(HAVE_OPENSSL,, Build with OpenSSL support)
-    LIBS="$LIBS $SSL_LIBS"
-  fi
-fi
-
-dnl **
-dnl ** Garbage Collector
-dnl **
-have_gc=no
-if test "x$want_gc" = xyes; then
-  AC_CHECK_LIB(gc, GC_malloc, [
-    AC_CHECK_HEADER(gc/gc.h, [
-      AC_DEFINE(HAVE_GC_GC_H)
-      AC_DEFINE(USE_GC)
-      LIBS="$LIBS -lgc"
-      have_gc=yes
-    ], [
-      AC_CHECK_HEADER(gc.h, [
-	AC_DEFINE(HAVE_GC_H)
-	AC_DEFINE(USE_GC)
-	LIBS="$LIBS -lgc"
-	have_gc=yes
-      ])
-    ])
-  ])
-fi
-
-dnl **
-dnl ** curses checks
-dnl **
-
-if test "x$want_textui" = "xyes"; then
-	AC_CHECK_CURSES
-
-	TEXTUI_LIBS="$CURSES_LIBS"
-	if test "x$has_curses" = "xtrue"; then
-		old_libs=$LIBS
-		LIBS="$LIBS $CURSES_LIBS"
-		if test $want_terminfo = no; then
-			AC_CHECK_FUNC(use_default_colors, AC_DEFINE(HAVE_NCURSES_USE_DEFAULT_COLORS))
-			AC_CHECK_FUNC(idcok, AC_DEFINE(HAVE_CURSES_IDCOK))
-			AC_CHECK_FUNC(resizeterm, AC_DEFINE(HAVE_CURSES_RESIZETERM))
-			AC_CHECK_FUNC(wresize, AC_DEFINE(HAVE_CURSES_WRESIZE))
-		fi
-		AC_CHECK_FUNC(setupterm,, [
-			want_termcap=yes
-		])
-		LIBS=$old_libs
-	else
-		AC_CHECK_LIB(tinfo, setupterm, [
-		  TEXTUI_LIBS="-ltinfo"
-		  want_terminfo=yes
-		], AC_CHECK_LIB(termlib, tgetent, [
-		  TEXTUI_LIBS="-ltermlib"
-		  want_termcap=yes
-		], AC_CHECK_LIB(termcap, tgetent, [
-		  TEXTUI_LIBS="-ltermcap"
-		  want_termcap=yes
-		], [
-		  AC_ERROR(Terminfo/termcap not found - install ncurses-devel package)
-		  want_textui=no
-		])))
-	fi
-	AC_SUBST(TEXTUI_LIBS)
-
-	if test "x$want_termcap" = "xyes"; then
-		AC_CHECK_FUNC(tparm,, need_tparm=yes)
-	else
-		AC_DEFINE(HAVE_TERMINFO)
-	fi
-fi
-
-dnl **
-dnl ** perl checks
-dnl **
-
-if test "$want_perl" != "no"; then
-	AC_MSG_CHECKING(for working Perl support)
-
-	if test -z "$perlpath"; then
-		perl_check_error="perl binary not found"
-	else
-		PERL_CFLAGS=`$perlpath -MExtUtils::Embed -e ccopts 2>/dev/null`
-	fi
-
-	if test "x$ac_cv_prog_gcc" = "xyes" -a -z "`echo $host_os|grep 'bsd\|linux'`"; then
-		dnl * several systems have Perl compiled with native compiler
-		dnl * but irssi is being compiled with GCC. Here we try to
-		dnl * fix those command line options a bit so GCC won't
-		dnl * complain about them. Normally there's only few options
-		dnl * that we want to keep:
-		dnl * -Ddefine -Uundef -I/path -fopt -mopt
-		PERL_CFLAGS=`echo $PERL_CFLAGS | $perlpath -pe 's/^(.* )?-[^DUIfm][^ ]+/\1/g; s/^(.* )?\+[^ ]+/\1/g'`
-
-		PERL_EXTRA_OPTS="CCCDLFLAGS=\"-fPIC\""
-		AC_SUBST(PERL_EXTRA_OPTS)
-	fi
-
-	if test -z "$PERL_CFLAGS"; then
-		if test -n "$perl_check_error"; then
-			perl_check_error="Error getting perl CFLAGS"
-		fi
-		AC_MSG_RESULT([not found, building without Perl])
-		want_perl=no
-	else
-		PERL_LDFLAGS=`$perlpath -MExtUtils::Embed -e ldopts 2>/dev/null`
-
-		dnl * remove all database stuffs
-		dnl * nsl is already in ldflags
-		dnl * libc is of course linked without needing -lc
-		dnl * -rdynamic must not be in LIBADD line
-		for word in -ldb -ldbm -lndbm -lgdbm -lc -rdynamic; do
-		  PERL_LDFLAGS=`echo $PERL_LDFLAGS | $sedpath -e "s/$word //" -e "s/$word$//"`
-		done
-
-		case "$host_os" in
-		  linux*)
-		    PERL_LDFLAGS=`echo $PERL_LDFLAGS | $sedpath -e 's/-lposix //' -e 's/-lposix$//'`
-		    ;;
-		  hpux*)
-		    if test "x$ac_cv_prog_gcc" = "xyes"; then
-		      PERL_CFLAGS=`echo $PERL_CFLAGS | $sedpath -e 's/-Ae //' -e 's/-Ae$//'`
-		      PERL_LDFLAGS=`echo $PERL_LDFLAGS | $sedpath -e 's/-Ae //' -e 's/-Ae$//'`
-		    fi
-		    ;;
-		  *)
-		    ;;
-		esac
-
-		dnl * check that perl's ldflags actually work
-		echo "main(){perl_alloc(); return 0;}" > conftest.c
-		$CC $CFLAGS conftest.c -o conftest $LDFLAGS $PERL_LDFLAGS 2> perl.error.tmp > /dev/null
-		if test ! -s conftest -a "x$ignore_perl_errors" = "x"; then
-			perl_check_error="Error linking with perl libraries: $PERL_LDFLAGS: `cat perl.error.tmp`"
-			AC_MSG_RESULT([error linking with perl libraries, building without Perl])
-			want_perl=no
-		fi
-
-		rm -f perl.error.tmp
-	fi
-
-	if test "x$want_perl" != "xno"; then
-		AC_MSG_RESULT(ok)
-
-		if test "x$want_perl" = "xstatic"; then
-			dnl * building with static perl support
-			dnl * all PERL_LDFLAGS linking is done in fe-text
-			PERL_LINK_FLAGS="$PERL_LDFLAGS"
-			PERL_LINK_LIBS="../perl/libperl_core_static.la"
-			PERL_FE_LINK_LIBS="../perl/libfe_perl_static.la"
-			PERL_LDFLAGS=
-			AC_DEFINE(HAVE_STATIC_PERL)
-
-			dnl * build only static library of perl module
-			perl_module_lib=
-			perl_module_fe_lib=
-			perl_static_lib=libperl_core_static.la
-			perl_static_fe_lib=libfe_perl_static.la
-		else
-			dnl * build dynamic library of perl module
-			perl_module_lib=libperl_core.la
-			perl_module_fe_lib=libfe_perl.la
-			perl_static_lib=
-			perl_static_fe_lib=
-		fi
-
-		if test "x$want_staticperllib" = "xyes"; then
-			PERL_MM_PARAMS="$PERL_MM_PARAMS LINKTYPE=static"
-			PERL_LINK_LIBS="$PERL_LINK_LIBS ../perl/common/blib/arch/auto/Irssi/Irssi.a ../perl/irc/blib/arch/auto/Irssi/Irc/Irc.a ../perl/ui/blib/arch/auto/Irssi/UI/UI.a ../perl/textui/blib/arch/auto/Irssi/TextUI/TextUI.a"
-			PERL_STATIC_LIBS=1
-		else
-			PERL_STATIC_LIBS=0
-		fi
-
-		# figure out the correct @INC path - we'll need to do this
-		# through MakeMaker since it's difficult to get it right
-		# otherwise.
-		if test "x$perl_set_use_lib" = "xyes"; then
-			perl -e 'use ExtUtils::MakeMaker; WriteMakefile("NAME" => "test", "MAKEFILE" => "Makefile.test");' $PERL_MM_PARAMS >/dev/null
-			PERL_USE_LIB=`perl -e 'open(F, "Makefile.test"); while (<F>) { chomp; if (/^(\w+) = (.*$)/) { $keys{$1} = $2; } }; $key = $keys{INSTALLARCHLIB}; while ($key =~ /\\$\((\w+)\)/) { $value = $keys{$1}; $key =~ s/\\$\($1\)/$value/; }; print $key;'`
-			rm -f Makefile.test
-		fi
-
-		AC_SUBST(perl_module_lib)
-		AC_SUBST(perl_static_lib)
-		AC_SUBST(perl_module_fe_lib)
-		AC_SUBST(perl_static_fe_lib)
-
-		AC_SUBST(PERL_LINK_FLAGS)
-		AC_SUBST(PERL_LINK_LIBS)
-		AC_SUBST(PERL_FE_LINK_LIBS)
-
-		AC_SUBST(PERL_LDFLAGS)
-		AC_SUBST(PERL_CFLAGS)
-
-		AC_SUBST(PERL_USE_LIB)
-		AC_SUBST(PERL_MM_PARAMS)
-		AC_SUBST(PERL_STATIC_LIBS)
-	fi
-fi
-
-dnl ** check what we want to build
-AM_CONDITIONAL(BUILD_TEXTUI, test "$want_textui" = "yes")
-AM_CONDITIONAL(BUILD_IRSSIBOT, test "$want_irssibot" = "yes")
-AM_CONDITIONAL(BUILD_IRSSIPROXY, test "$want_irssiproxy" = "yes")
-AM_CONDITIONAL(HAVE_PERL, test "$want_perl" != "no")
-AM_CONDITIONAL(NEED_TPARM, test "$need_tparm" = "yes")
-AM_CONDITIONAL(USE_CURSES, test "$want_terminfo" != "yes" -a "$want_termcap" != "yes")
-
-# move LIBS to PROG_LIBS so they're not tried to be used when linking eg. perl libraries
-PROG_LIBS=$LIBS
-LIBS=
-AC_SUBST(PROG_LIBS)
-
-dnl **
-dnl ** Keep all the libraries here so each frontend doesn't need to
-dnl ** keep track of them all
-dnl **
-dnl ** (these could be made configurable)
-
-CHAT_MODULES="irc"
-irc_MODULES="dcc flood notifylist"
-if test -n "$build_modules"; then
-	irc_MODULES="$irc_MODULES $build_modules"
-fi
-
-dnl ****************************************
-
-AC_SUBST(CHAT_MODULES)
-AC_SUBST(irc_MODULES)
-
-CORE_LIBS="../core/libcore.a ../lib-config/libirssi_config.a"
-FE_COMMON_LIBS=""
-
-CHAT_LIBS=""
-for c in $CHAT_MODULES; do
-	module_inits=""
-	module_deinits=""
-	fe_module_inits=""
-	fe_module_deinits=""
-	CHAT_LIBS="$CHAT_LIBS ../$c/lib$c.a ../$c/core/lib${c}_core.a"
-	if test -f $srcdir/src/fe-common/$c/module.h; then
-		FE_COMMON_LIBS="$FE_COMMON_LIBS../fe-common/$c/libfe_common_$c.a "
-	fi
-	for s in `eval echo \\$${c}_MODULES`; do
-		CHAT_LIBS="$CHAT_LIBS ../$c/$s/lib${c}_$s.a"
-		module_inits="$module_inits ${c}_${s}_init();"
-		module_deinits="${c}_${s}_deinit(); $module_deinits"
-		if test -f $srcdir/src/fe-common/$c/$s/module.h; then
-			FE_COMMON_LIBS="$FE_COMMON_LIBS../fe-common/$c/$s/libfe_${c}_$s.a "
-			fe_module_inits="$fe_module_inits fe_${c}_${s}_init();"
-			fe_module_deinits="fe_${c}_${s}_deinit(); $fe_module_deinits"
-		fi
-	done
-
-	mkdir -p src/$c
-	file="src/$c/$c.c"
-	echo "/* this file is automatically generated by configure - don't change */" > $file
-	echo "void ${c}_core_init(void); void ${c}_core_deinit(void);" >> $file
-	if test -n "$module_inits"; then
-		echo "$module_inits" | $sedpath -e 's/()/(void)/g' -e 's/ /void /g' >> $file
-		echo "$module_deinits" | $sedpath -e 's/ *$//' -e 's/()/(void)/g' -e 's/ /void /g' -e 's/^/void /' >> $file
-	fi
-	echo "void ${c}_init(void) { ${c}_core_init(); $module_inits }" >> $file
-	echo "void ${c}_deinit(void) { $module_deinits ${c}_core_deinit(); }" >> $file
-
-	if test -f $srcdir/src/fe-common/$c/module.h; then
-		mkdir -p src/fe-common/$c
-		file="src/fe-common/$c/${c}-modules.c"
-		echo "/* this file is automatically generated by configure - don't change */" > $file
-		if test -n "$fe_module_inits"; then
-			echo "$fe_module_inits" | $sedpath -e 's/()/(void)/g' -e 's/ /void /g' >> $file
-			echo "$fe_module_deinits" | $sedpath -e 's/ *$//' -e 's/()/(void)/g' -e 's/ /void /g' -e 's/^/void /' >> $file
-		fi
-		echo "void fe_${c}_modules_init(void) { $fe_module_inits }" >> $file
-		echo "void fe_${c}_modules_deinit(void) { $fe_module_deinits }" >> $file
-	fi
-done
-
-FE_COMMON_LIBS="$FE_COMMON_LIBS../fe-common/core/libfe_common_core.a"
-
-dnl ** common libraries needed by frontends
-COMMON_NOUI_LIBS="$CHAT_LIBS $CORE_LIBS"
-COMMON_LIBS="$FE_COMMON_LIBS $COMMON_NOUI_LIBS"
-AC_SUBST(COMMON_NOUI_LIBS)
-AC_SUBST(COMMON_LIBS)
-
-dnl **
-dnl ** IPv6 support
-dnl **
-
-have_ipv6=no
-if test "x$want_ipv6" = "xyes"; then
-	AC_MSG_CHECKING([for IPv6])
-	AC_CACHE_VAL(irssi_cv_type_in6_addr,
-	[AC_TRY_COMPILE([
-	#include <sys/types.h>
-	#include <sys/socket.h>
-	#include <netinet/in.h>
-	#include <netdb.h>
-	#include <arpa/inet.h>],
-	[struct in6_addr i;],
-	have_ipv6=yes,
-	)])
-	if test $have_ipv6 = yes; then
-		AC_DEFINE(HAVE_IPV6)
-	fi
-	AC_MSG_RESULT($have_ipv6)
-fi
-
-AC_CONFIG_FILES([
-Makefile
-src/Makefile
-src/core/Makefile
-src/irc/Makefile
-src/irc/core/Makefile
-src/irc/dcc/Makefile
-src/irc/notifylist/Makefile
-src/irc/proxy/Makefile
-src/irc/flood/Makefile
-src/fe-common/Makefile
-src/fe-common/core/Makefile
-src/fe-common/irc/Makefile
-src/fe-common/irc/dcc/Makefile
-src/fe-common/irc/notifylist/Makefile
-src/fe-none/Makefile
-src/fe-text/Makefile
-src/lib-config/Makefile
-src/perl/Makefile
-src/perl/common/Makefile.PL
-src/perl/irc/Makefile.PL
-src/perl/ui/Makefile.PL
-src/perl/textui/Makefile.PL
-scripts/Makefile
-scripts/examples/Makefile
-docs/Makefile
-docs/help/Makefile
-docs/help/in/Makefile
-irssi-config
-])
-
-AC_OUTPUT
-
-dnl ** for building from objdir
-old_dir=`pwd` && cd $srcdir && whole_dir=`pwd` && cd $old_dir
-if test "x$old_dir" != "x$whole_dir"; then
-	if test "x$want_perl" != "xno"; then
-		subdirfiles=""
-		for i in $whole_dir/src/perl/common $whole_dir/src/perl/irc $whole_dir/src/perl/ui $whole_dir/src/perl/textui; do
-			subdirfiles=`echo $subdirfiles $i/typemap $i/module.h $i/*.pm $i/*.xs`
-		done
-		for file in $whole_dir/src/perl/module.h $subdirfiles; do
-			link=`echo $file|$sedpath "s?$whole_dir/??"`
-			rm -f $link
-			$LN_S $file $link
-		done
-	fi
-fi
-
-echo
-
-if test "x$want_textui" = "xno"; then
-	text=no
-elif test "x$want_termcap" = "xyes"; then
-	text="yes, using termcap"
-elif test "x$want_terminfo" = "xyes"; then
-	text="yes, using terminfo"
-else
-	text="yes, using curses"
-fi
-echo "Building text frontend ........... : $text"
-echo "Building irssi bot ............... : $want_irssibot"
-echo "Building irssi proxy ............. : $want_irssiproxy"
-if test "x$have_gmodule" = "xyes"; then
-	echo "Building with module support ..... : yes"
-else
-	echo "Building with module support : NO!! /LOAD will not work!"
-	echo " - You're missing gmodule (comes with glib) for some reason,"
-	echo "   or it doesn't work in your system."
-fi
-
-if test "x$want_perl" = "xstatic"; then
-	echo "Building with Perl support ....... : static (in irssi binary)"
-elif test "x$want_perl" = "xmodule"; then
-	echo "Building with Perl support ....... : module"
-else
-	if test -z "$perl_check_error"; then
-		echo "Building with Perl support ....... : no"
-	else
-		echo "Building with Perl support ....... : NO!"
-		echo " - $perl_check_error"
-	fi
-fi
-
-if test "x$want_perl" != "xno" -a "x$perl_mod_error" != "x"; then
-	echo " - NOTE: Perl support will be compiled statically to irssi, not as"
-	echo "   a module as requested. Reason:"
-	echo "   $perl_mod_error"
-
-	if test -f /etc/debian_version; then
-		echo " - Try: apt-get install libperl-dev"
-	fi
-fi
-
-if test "x$want_perl" != "xno"; then
-	if test "$perl_library_dir" = "PERL_USE_LIB"; then
-		perl_library_dir=$PERL_USE_LIB
-	fi
-	if test -z "$perl_library_dir"; then
-		perl_library_dir="(site default - `$perlpath -e 'use Config; print $Config{sitearch}'`)"
-	fi
-	echo "Perl library directory ........... : $perl_library_dir"
-	if test "x$perl_prefix_note" = "xyes"; then
-		echo "  - NOTE: This was automatically set to the same directory you gave with"
-		echo "  --prefix. If you want the perl libraries to install to their 'correct'"
-		echo "  path, you'll need to give --with-perl-lib=site option to configure."
-		echo "  Anyway, installing perl to this directory should work just as well."
-	fi
-fi
-echo "Install prefix ................... : $prefix"
-
-echo
-
-echo "Building with IPv6 support ....... : $have_ipv6"
-echo "Building with SSL support ........ : $have_openssl"
-echo "Building with 64bit DCC support .. : $offt_64bit"
-echo "Building with garbage collector .. : $have_gc"
-
-echo
-echo "If there are any problems, read the INSTALL file."

curses.m4

@@ -1,298 +0,0 @@
-dnl Curses detection: Munged from Midnight Commander's configure.in
-dnl
-dnl What it does:
-dnl =============
-dnl
-dnl - Determine which version of curses is installed on your system
-dnl   and set the -I/-L/-l compiler entries and add a few preprocessor
-dnl   symbols
-dnl - Do an AC_SUBST on the CURSES_INCLUDEDIR and CURSES_LIBS so that
-dnl   @CURSES_INCLUDEDIR@ and @CURSES_LIBS@ will be available in
-dnl   Makefile.in's
-dnl - Modify the following configure variables (these are the only
-dnl   curses.m4 variables you can access from within configure.in)
-dnl   CURSES_INCLUDEDIR - contains -I's and possibly -DRENAMED_CURSES if
-dnl                       an ncurses.h that's been renamed to curses.h
-dnl                       is found.
-dnl   CURSES_LIBS       - sets -L and -l's appropriately
-dnl   CFLAGS            - if --with-sco, add -D_SVID3
-dnl   has_curses        - exports result of tests to rest of configure
-dnl
-dnl Usage:
-dnl ======
-dnl 1) Add lines indicated below to acconfig.h
-dnl 2) call AC_CHECK_CURSES after AC_PROG_CC in your configure.in
-dnl 3) Instead of #include <curses.h> you should use the following to
-dnl    properly locate ncurses or curses header file
-dnl
-dnl    #if defined(USE_NCURSES) && !defined(RENAMED_NCURSES)
-dnl    #include <ncurses.h>
-dnl    #else
-dnl    #include <curses.h>
-dnl    #endif
-dnl
-dnl 4) Make sure to add @CURSES_INCLUDEDIR@ to your preprocessor flags
-dnl 5) Make sure to add @CURSES_LIBS@ to your linker flags or LIBS
-dnl
-dnl Notes with automake:
-dnl - call AM_CONDITIONAL(HAS_CURSES, test "$has_curses" = true) from
-dnl   configure.in
-dnl - your Makefile.am can look something like this
-dnl   -----------------------------------------------
-dnl   INCLUDES= blah blah blah $(CURSES_INCLUDEDIR)
-dnl   if HAS_CURSES
-dnl   CURSES_TARGETS=name_of_curses_prog
-dnl   endif
-dnl   bin_PROGRAMS = other_programs $(CURSES_TARGETS)
-dnl   other_programs_SOURCES = blah blah blah
-dnl   name_of_curses_prog_SOURCES = blah blah blah
-dnl   other_programs_LDADD = blah
-dnl   name_of_curses_prog_LDADD = blah $(CURSES_LIBS)
-dnl   -----------------------------------------------
-dnl
-dnl
-dnl The following lines should be added to acconfig.h:
-dnl ==================================================
-dnl
-dnl /*=== Curses version detection defines ===*/
-dnl /* Found some version of curses that we're going to use */
-dnl #undef HAS_CURSES
-dnl   
-dnl /* Use SunOS SysV curses? */
-dnl #undef USE_SUNOS_CURSES
-dnl
-dnl /* Use old BSD curses - not used right now */
-dnl #undef USE_BSD_CURSES
-dnl
-dnl /* Use SystemV curses? */
-dnl #undef USE_SYSV_CURSES
-dnl
-dnl /* Use Ncurses? */
-dnl #undef USE_NCURSES
-dnl
-dnl /* If you Curses does not have color define this one */
-dnl #undef NO_COLOR_CURSES
-dnl
-dnl /* Define if you want to turn on SCO-specific code */
-dnl #undef SCO_FLAVOR
-dnl
-dnl /* Set to reflect version of ncurses *
-dnl  *   0 = version 1.*
-dnl  *   1 = version 1.9.9g
-dnl  *   2 = version 4.0/4.1 */
-dnl #undef NCURSES_970530
-dnl
-dnl /*=== End new stuff for acconfig.h ===*/
-dnl
-
-
-AC_DEFUN([AC_CHECK_CURSES],[
-	search_ncurses=true
-	screen_manager=""
-	has_curses=false
-
-	CFLAGS=${CFLAGS--O}
-
-	AC_SUBST(CURSES_LIBS)
-	AC_SUBST(CURSES_INCLUDEDIR)
-
-	AC_ARG_WITH(sco,
-	  [  --with-sco              Use this to turn on SCO-specific code],[
-	  if test x$withval = xyes; then
-		AC_DEFINE(SCO_FLAVOR)
-		CFLAGS="$CFLAGS -D_SVID3"
-	  fi
-	])
-
-	AC_ARG_WITH(sunos-curses,
-	  [  --with-sunos-curses     Used to force SunOS 4.x curses],[
-	  if test x$withval = xyes; then
-		AC_USE_SUNOS_CURSES
-	  fi
-	])
-
-	AC_ARG_WITH(osf1-curses,
-	  [  --with-osf1-curses      Used to force OSF/1 curses],[
-	  if test x$withval = xyes; then
-		AC_USE_OSF1_CURSES
-	  fi
-	])
-
-	AC_ARG_WITH(vcurses,
-	  [[  --with-vcurses[=incdir] Used to force SysV curses]],
-	  if test x$withval != xyes; then
-		CURSES_INCLUDEDIR="-I$withval"
-	  fi
-	  AC_USE_SYSV_CURSES
-	)
-
-	AC_ARG_WITH(ncurses,
-	  [[  --with-ncurses[=dir]    Compile with ncurses/locate base dir]],
-	  if test x$withval = xno ; then
-		search_ncurses=false
-	  elif test x$withval != xyes ; then
-		AC_NCURSES($withval/include, ncurses.h, -L$withval/lib -lncurses, -I$withval/include, "ncurses on $withval/include")
-	  fi
-	)
-
-	if $search_ncurses
-	then
-		AC_SEARCH_NCURSES()
-	fi
-])
-
-
-AC_DEFUN([AC_USE_SUNOS_CURSES], [
-	search_ncurses=false
-	screen_manager="SunOS 4.x /usr/5include curses"
-	AC_MSG_RESULT(Using SunOS 4.x /usr/5include curses)
-	AC_DEFINE(USE_SUNOS_CURSES)
-	AC_DEFINE(HAS_CURSES)
-	has_curses=true
-	AC_DEFINE(NO_COLOR_CURSES)
-	AC_DEFINE(USE_SYSV_CURSES)
-	CURSES_INCLUDEDIR="-I/usr/5include"
-	CURSES_LIBS="/usr/5lib/libcurses.a /usr/5lib/libtermcap.a"
-	AC_MSG_RESULT(Please note that some screen refreshs may fail)
-])
-
-AC_DEFUN([AC_USE_OSF1_CURSES], [
-       AC_MSG_RESULT(Using OSF1 curses)
-       search_ncurses=false
-       screen_manager="OSF1 curses"
-       AC_DEFINE(HAS_CURSES)
-       has_curses=true
-       AC_DEFINE(NO_COLOR_CURSES)
-       AC_DEFINE(USE_SYSV_CURSES)
-       CURSES_LIBS="-lcurses"
-])
-
-AC_DEFUN([AC_USE_SYSV_CURSES], [
-	AC_MSG_RESULT(Using SysV curses)
-	AC_DEFINE(HAS_CURSES)
-	has_curses=true
-	AC_DEFINE(USE_SYSV_CURSES)
-	search_ncurses=false
-	screen_manager="SysV/curses"
-	CURSES_LIBS="-lcurses"
-])
-
-dnl AC_ARG_WITH(bsd-curses,
-dnl [--with-bsd-curses         Used to compile with bsd curses, not very fancy],
-dnl 	search_ncurses=false
-dnl	screen_manager="Ultrix/cursesX"
-dnl	if test $system = ULTRIX
-dnl	then
-dnl	    THIS_CURSES=cursesX
-dnl        else
-dnl	    THIS_CURSES=curses
-dnl	fi
-dnl
-dnl	CURSES_LIBS="-l$THIS_CURSES -ltermcap"
-dnl	AC_DEFINE(HAS_CURSES)
-dnl	has_curses=true
-dnl	AC_DEFINE(USE_BSD_CURSES)
-dnl	AC_MSG_RESULT(Please note that some screen refreshs may fail)
-dnl	AC_WARN(Use of the bsdcurses extension has some)
-dnl	AC_WARN(display/input problems.)
-dnl	AC_WARN(Reconsider using xcurses)
-dnl)
-
-
-dnl
-dnl Parameters: directory filename curses_LIBS curses_INCLUDEDIR nicename
-dnl
-AC_DEFUN([AC_NCURSES], [
-    if $search_ncurses
-    then
-        if test -f $1/$2
-	then
-	    AC_MSG_RESULT(Found ncurses on $1/$2)
-
-	    CURSES_LIBS="$3"
-	    AC_CHECK_LIB(ncurses, initscr, [
-	        true;
-	    ], [
-                CHECKLIBS=`echo "$3"|sed 's/-lncurses/-lcurses/g'`
-		AC_CHECK_LIB(curses, initscr, [
-			CURSES_LIBS="$CHECKLIBS"
-		],, $CHECKLIBS)
-	    ], $CURSES_LIBS)
-	    CURSES_INCLUDEDIR="$4"
-	    search_ncurses=false
-	    screen_manager="$5"
-            AC_DEFINE(HAS_CURSES)
-            has_curses=true
-	    has_ncurses=true
-	    AC_DEFINE(USE_NCURSES)
-	fi
-    fi
-])
-
-AC_DEFUN([AC_SEARCH_NCURSES], [
-    AC_CHECKING("location of ncurses.h file")
-
-    AC_NCURSES(/usr/include, ncurses.h, -lncurses,,
-	       [ncurses in /usr/include])
-    AC_NCURSES(/usr/include/ncurses, ncurses.h, -lncurses, -I/usr/include/ncurses,
-	       [ncurses in /usr/include/ncurses])
-    AC_NCURSES(/usr/local/include, ncurses.h, -L/usr/local/lib -lncurses, -I/usr/local/include,
-	       [ncurses in /usr/local/include])
-    AC_NCURSES(/usr/local/include/ncurses, ncurses.h, -L/usr/local/lib -lncurses, -I/usr/local/include/ncurses,
-	       [ncurses in /usr/local/include/ncurses])
-    AC_NCURSES(/usr/local/include/ncurses, curses.h, -L/usr/local/lib -lncurses, -I/usr/local/include/ncurses -DRENAMED_NCURSES,
-	       [renamed ncurses in /usr/local/include/ncurses])
-    AC_NCURSES(/usr/include/ncurses, curses.h, -lncurses, -I/usr/include/ncurses -DRENAMED_NCURSES,
-	       [renamed ncurses in /usr/include/ncurses])
-
-    dnl
-    dnl We couldn't find ncurses, try SysV curses
-    dnl
-    if $search_ncurses
-    then
-        AC_EGREP_HEADER(init_color, /usr/include/curses.h,
-	    AC_USE_SYSV_CURSES)
-	AC_EGREP_CPP(USE_NCURSES,[
-#include <curses.h>
-#ifdef __NCURSES_H
-#undef USE_NCURSES
-USE_NCURSES
-#endif
-],[
-	CURSES_INCLUDEDIR="$CURSES_INCLUDEDIR -DRENAMED_NCURSES"
-        AC_DEFINE(HAS_CURSES)
-	has_curses=true
-	has_ncurses=true
-        AC_DEFINE(USE_NCURSES)
-        search_ncurses=false
-        screen_manager="ncurses installed as curses"
-])
-    fi
-
-    dnl
-    dnl Try SunOS 4.x /usr/5{lib,include} ncurses
-    dnl The flags USE_SUNOS_CURSES, USE_BSD_CURSES and BUGGY_CURSES
-    dnl should be replaced by a more fine grained selection routine
-    dnl
-    if $search_ncurses
-    then
-	if test -f /usr/5include/curses.h
-	then
-	    AC_USE_SUNOS_CURSES
-        fi
-    fi
-
-    dnl use whatever curses there happens to be
-    if $search_ncurses
-    then
-	if test -f /usr/include/curses.h
-	then
-	  CURSES_LIBS="-lcurses"
-	  AC_DEFINE(HAS_CURSES)
-	  has_curses=true
-	  search_ncurses=false
-	  screen_manager="curses"
-	fi
-    fi
-])
-

docs/Makefile.am

@@ -1,19 +0,0 @@
-docdir = $(datadir)/doc/irssi
-
-man_MANS = \
-	irssi.1
-
-doc_DATA = \
-	design.txt \
-	formats.txt \
-	manual.txt \
-	faq.html \
-	faq.txt \
-	perl.txt \
-	signals.txt \
-	special_vars.txt \
-	startup-HOWTO.html
-
-EXTRA_DIST = $(doc_DATA) $(man_MANS)
-
-SUBDIRS = help

docs/New-users.html

@@ -0,0 +1,110 @@
+<base href='https://irssi.org/New-users/'>
+<h1>New users guide</h1>
+<section id="new-to-irc">
+<h2>New to IRC</h2>
+<p>Internet Relay Chat was created in 1988 and has hardly changed. It can be used to exchange text messages (one message = single line) with other people, either privately (called query, PM, private message, MSG) or in a room (channel). Pictures are shared by uploading them to a temporary host like <a class="reference external" href="https://pomf.lain.la/">https://pomf.lain.la/</a> and then pasting the HTTP links. Code snippets or longer texts are shared by pasting them to a Pastebin like <a class="reference external" href="https://paste.opensuse.org/">https://paste.opensuse.org/</a> and then sharing the HTTP link.</p>
+<p>IRC does not have message history. You can only receive replies while your computer is turned on and connected to the channel you want to follow. Some people run their IRC programs on remote servers for that reason.</p>
+<p>IRC is organised into networks. Each network consists of many servers. It (mostly) does not matter which server you connect to as long as it belongs to the network you want to use. Irssi supports connections to many networks at the same time.</p>
+<p>Each network contains many channels, rooms that are often dedicated to discussing a specific topic. You can find many channels on <a class="reference external" href="https://netsplit.de/">https://netsplit.de/</a> or using a search engine with the keyword “IRC”. Irssi supports joining many channels at the same time.</p>
+<p>There is a rather large IRC network catering to free and open-source software and peer directed projects at <a class="reference external" href="https://libera.chat/">https://libera.chat/</a> and a smaller one at <a class="reference external" href="https://www.oftc.net/">https://www.oftc.net/</a> – many free software projects still have support channels on these IRC networks (although some have moved to Matrix or proprietary platforms like Discord).</p>
+</section>
+<section id="first-start">
+<h2>First start</h2>
+<p>After (compiling and) installing Irssi, to start it, open a shell (Terminal) and type:</p>
+<div class="highlight-default notranslate"><div><pre>irssi
+</pre></div>
+</div>
+<p>You should be greeted by a blinking cursor behind <code class="docutils literal notranslate">[(status)]</code>. You are now in the status window of Irssi. Window is the Irssi name for what you might nowadays call a “Web browser tab”.</p>
+<p>If you’re confused about what you are seeing on the Irssi screen, you can find an annotated screenshot of it at <a class="reference internal" href="../User-interface/">User interface</a>.</p>
+<p>If you want, you can pick a nick name (handle) that will be shown to others reading your messages now, by typing</p>
+<div class="highlight-default notranslate"><div><pre>/set nick whatyouwant
+</pre></div>
+</div>
+<p>Each command or message can be sent by pressing Enter. Commands in Irssi start with a <code class="docutils literal notranslate">/</code>. If there is no <code class="docutils literal notranslate">/</code>, then the line that you wrote will be sent as a message to the channel that you have open, for everyone to see.</p>
+<section id="leaving">
+<h3>Leaving</h3>
+<p>Type <code class="docutils literal notranslate">/quit</code> to get out of Irssi.</p>
+</section>
+</section>
+<section id="connecting-to-a-network">
+<h2>Connecting to a network</h2>
+<p>Irssi comes with some predefined networks. You can see the current list of networks by typing</p>
+<div class="highlight-default notranslate"><div><pre>/network
+</pre></div>
+</div>
+<p>(the list will be shown in your status window)</p>
+<p>To connect to one of the networks in the list, type <code class="docutils literal notranslate">/connect networkname</code>, for example:</p>
+<div class="highlight-default notranslate"><div><pre>/connect liberachat
+</pre></div>
+</div>
+<p>You should see several messages scroll by. After a while, you should be connected to the Libera Chat network.</p>
+<div class="admonition attention">
+<p class="admonition-title">Attention</p>
+<p>Irssi version 1.2 or older may be lacking the liberachat network entry. See <a class="reference external" href="https://github.com/shabble/irssi-docs/wiki/liberachat">https://github.com/shabble/irssi-docs/wiki/liberachat</a> for how to add it.</p>
+</div>
+<section id="nickname-registration">
+<h3>Nickname registration</h3>
+<p>Many IRC networks (but not all) offer a way to register a user account. Sometimes (but not on all networks) the account registration also includes reserving a nick for you. <em>How</em> to register also differs by network. Some <em>channels</em> only allow users with registered accounts to join them, so it may be very important for you to register a user account.</p>
+<p>User accounts are always specific to a network.</p>
+<p>For the Libera Chat network, you can find instructions how to register and set up your account with Irssi on <a class="reference external" href="https://github.com/shabble/irssi-docs/wiki/liberachat#configure-sasl-automated-log-in">https://github.com/shabble/irssi-docs/wiki/liberachat#configure-sasl-automated-log-in</a></p>
+</section>
+</section>
+<section id="joining-a-channel">
+<h2>Joining a channel</h2>
+<p>Once you are connected to a network, you can join channels by typing <code class="docutils literal notranslate">/join #channelname</code>, for example:</p>
+<div class="highlight-default notranslate"><div><pre>/join #irssi
+</pre></div>
+</div>
+<p>Now, a new window will open and you can send messages to the channel.</p>
+<section id="changing-windows">
+<h3>Changing windows</h3>
+<p>You can change between windows using the <code class="docutils literal notranslate">Ctrl</code>+<code class="docutils literal notranslate">n</code> or <code class="docutils literal notranslate">Ctrl</code>+<code class="docutils literal notranslate">p</code> keys, or–if your terminal is configured properly–using <code class="docutils literal notranslate">Alt</code>+<code class="docutils literal notranslate">1</code>, <code class="docutils literal notranslate">Alt</code>+<code class="docutils literal notranslate">2</code>, … See <a class="reference internal" href="../documentation/help/bind_-list/">bind -list</a> for a list of all default key bindings.</p>
+</section>
+<section id="removing-clutter">
+<h3>Removing clutter</h3>
+<p>By default, Irssi shows when someone joins or leaves a channel. These messages can waste a lot of lines and obscure the actual chat. To hide them, type</p>
+<div class="highlight-default notranslate"><div><pre>/window hidelevel +joins +parts +quits
+</pre></div>
+</div>
+<p>To get them back</p>
+<div class="highlight-default notranslate"><div><pre>/window hidelevel -joins -parts -quits
+</pre></div>
+</div>
+<p>If you want to hide them by default, <code class="docutils literal notranslate">/set window_default_hidelevel hidden joins parts quits</code></p>
+</section>
+</section>
+<section id="adding-a-new-network">
+<h2>Adding a new network</h2>
+<p>If you want to join a network that is not there, you first need to find at least one server of that network. Let’s say you have found the room <a class="reference external" href="https://netsplit.de/channels/details.php?room=%23hackint&amp;net=hackint">#hackint</a> on netsplit.de and want to join it. Then you can find that the <a class="reference external" href="https://netsplit.de/servers/?net=hackint">server</a> is irc.hackint.org, port 6697, SSL (TLS) on. To add it to Irssi, use the commands:</p>
+<div class="highlight-default notranslate"><div><pre>/network add hackint
+/server add -tls -network hackint irc.hackint.org 6697
+</pre></div>
+</div>
+<p>Then, you can connect to the newly added network with</p>
+<div class="highlight-default notranslate"><div><pre>/connect hackint
+</pre></div>
+</div>
+<section id="multiple-networks">
+<h3>Multiple networks</h3>
+<p>If you are connected to multiple networks, you can change which one you are “talking” to (which one to send commands) by using the <code class="docutils literal notranslate">Ctrl</code>+<code class="docutils literal notranslate">x</code> key in the status window.</p>
+</section>
+</section>
+<section id="on-line-help">
+<h2>On-line help</h2>
+<p>Most /commands have a help page, you can read it with</p>
+<div class="highlight-default notranslate"><div><pre>/help commandname
+</pre></div>
+</div>
+<p>or <a class="reference internal" href="../documentation/help/">on-line</a>.</p>
+<p>The settings that can be changed with /SET are described on <a class="reference internal" href="../documentation/settings/">Settings Documentation</a> – the settingshelp <a class="reference internal" href="#about-scripts">script</a> can be used to read it from within <code class="docutils literal notranslate">/help</code></p>
+</section>
+<section id="about-scripts">
+<h2>About Scripts</h2>
+<p>You can enhance your Irssi by installing scripts. Many Perl scripts written by other Irssi users can be found on <a class="reference external" href="https://scripts.irssi.org/">https://scripts.irssi.org/</a></p>
+<p>Most of them should be compatible with Irssi 1.4 (but some may not, also see the Full Change log for some incompatible ones)</p>
+</section>
+<section id="about-themes">
+<h2>About Themes</h2>
+<p>Irssi’s look can be thoroughly changed with themes. Many themes created by other Irssi users can be found on <a class="reference external" href="https://themes.irssi.org/">https://themes.irssi.org/</a></p>
+<p>If you want to modify the look of Irssi yourself, the <em>default</em> theme which can be found in your <code class="docutils literal notranslate">~/.irssi</code> folder is a good starting point. It also has a few comments explaining what some of the abstracts are used for</p>
+</section>

docs/New-users.txt

@@ -0,0 +1,193 @@
+# New users guide #
+
+## New to IRC ##
+
+Internet Relay Chat was created in 1988 and has hardly changed. It can be used
+to exchange text messages (one message = single line) with other people, either
+privately (called query, PM, private message, MSG) or in a room (channel).
+Pictures are shared by uploading them to a temporary host like [1]https://
+pomf.lain.la/ and then pasting the HTTP links. Code snippets or longer texts
+are shared by pasting them to a Pastebin like [2]https://paste.opensuse.org/
+and then sharing the HTTP link.
+
+IRC does not have message history. You can only receive replies while your
+computer is turned on and connected to the channel you want to follow. Some
+people run their IRC programs on remote servers for that reason.
+
+IRC is organised into networks. Each network consists of many servers. It
+(mostly) does not matter which server you connect to as long as it belongs to
+the network you want to use. Irssi supports connections to many networks at the
+same time.
+
+Each network contains many channels, rooms that are often dedicated to
+discussing a specific topic. You can find many channels on [3]https://
+netsplit.de/ or using a search engine with the keyword “IRC”. Irssi supports
+joining many channels at the same time.
+
+There is a rather large IRC network catering to free and open-source software
+and peer directed projects at [4]https://libera.chat/ and a smaller one at [5]
+https://www.oftc.net/ – many free software projects still have support channels
+on these IRC networks (although some have moved to Matrix or proprietary
+platforms like Discord).
+
+## First start ##
+
+After (compiling and) installing Irssi, to start it, open a shell (Terminal)
+and type:
+
+irssi
+
+You should be greeted by a blinking cursor behind [(status)]. You are now in
+the status window of Irssi. Window is the Irssi name for what you might
+nowadays call a “Web browser tab”.
+
+If you’re confused about what you are seeing on the Irssi screen, you can find
+an annotated screenshot of it at [6]User interface.
+
+If you want, you can pick a nick name (handle) that will be shown to others
+reading your messages now, by typing
+
+/set nick whatyouwant
+
+Each command or message can be sent by pressing Enter. Commands in Irssi start
+with a /. If there is no /, then the line that you wrote will be sent as a
+message to the channel that you have open, for everyone to see.
+
+### Leaving ###
+
+Type /quit to get out of Irssi.
+
+## Connecting to a network ##
+
+Irssi comes with some predefined networks. You can see the current list of
+networks by typing
+
+/network
+
+(the list will be shown in your status window)
+
+To connect to one of the networks in the list, type /connect networkname, for
+example:
+
+/connect liberachat
+
+You should see several messages scroll by. After a while, you should be
+connected to the Libera Chat network.
+
+Attention
+
+Irssi version 1.2 or older may be lacking the liberachat network entry. See [7]
+https://github.com/shabble/irssi-docs/wiki/liberachat for how to add it.
+
+### Nickname registration ###
+
+Many IRC networks (but not all) offer a way to register a user account.
+Sometimes (but not on all networks) the account registration also includes
+reserving a nick for you. How to register also differs by network. Some
+channels only allow users with registered accounts to join them, so it may be
+very important for you to register a user account.
+
+User accounts are always specific to a network.
+
+For the Libera Chat network, you can find instructions how to register and set
+up your account with Irssi on [8]https://github.com/shabble/irssi-docs/wiki/
+liberachat#configure-sasl-automated-log-in
+
+## Joining a channel ##
+
+Once you are connected to a network, you can join channels by typing /join #
+channelname, for example:
+
+/join #irssi
+
+Now, a new window will open and you can send messages to the channel.
+
+### Changing windows ###
+
+You can change between windows using the Ctrl+n or Ctrl+p keys, or–if your
+terminal is configured properly–using Alt+1, Alt+2, … See [9]bind -list for a
+list of all default key bindings.
+
+### Removing clutter ###
+
+By default, Irssi shows when someone joins or leaves a channel. These messages
+can waste a lot of lines and obscure the actual chat. To hide them, type
+
+/window hidelevel +joins +parts +quits
+
+To get them back
+
+/window hidelevel -joins -parts -quits
+
+If you want to hide them by default, /set window_default_hidelevel hidden joins
+parts quits
+
+## Adding a new network ##
+
+If you want to join a network that is not there, you first need to find at
+least one server of that network. Let’s say you have found the room [10]#
+hackint on netsplit.de and want to join it. Then you can find that the [11]
+server is irc.hackint.org, port 6697, SSL (TLS) on. To add it to Irssi, use the
+commands:
+
+/network add hackint
+/server add -tls -network hackint irc.hackint.org 6697
+
+Then, you can connect to the newly added network with
+
+/connect hackint
+
+### Multiple networks ###
+
+If you are connected to multiple networks, you can change which one you are
+“talking” to (which one to send commands) by using the Ctrl+x key in the status
+window.
+
+## On-line help ##
+
+Most /commands have a help page, you can read it with
+
+/help commandname
+
+or [12]on-line.
+
+The settings that can be changed with /SET are described on [13]Settings
+Documentation – the settingshelp [14]script can be used to read it from within
+/help
+
+## About Scripts ##
+
+You can enhance your Irssi by installing scripts. Many Perl scripts written by
+other Irssi users can be found on [15]https://scripts.irssi.org/
+
+Most of them should be compatible with Irssi 1.4 (but some may not, also see
+the Full Change log for some incompatible ones)
+
+## About Themes ##
+
+Irssi’s look can be thoroughly changed with themes. Many themes created by
+other Irssi users can be found on [16]https://themes.irssi.org/
+
+If you want to modify the look of Irssi yourself, the default theme which can
+be found in your ~/.irssi folder is a good starting point. It also has a few
+comments explaining what some of the abstracts are used for
+
+
+References:
+
+[1] https://pomf.lain.la/
+[2] https://paste.opensuse.org/
+[3] https://netsplit.de/
+[4] https://libera.chat/
+[5] https://www.oftc.net/
+[6] https://irssi.org/User-interface/
+[7] https://github.com/shabble/irssi-docs/wiki/liberachat
+[8] https://github.com/shabble/irssi-docs/wiki/liberachat#configure-sasl-automated-log-in
+[9] https://irssi.org/documentation/help/bind_-list/
+[10] https://netsplit.de/channels/details.php?room=%23hackint&net=hackint
+[11] https://netsplit.de/servers/?net=hackint
+[12] https://irssi.org/documentation/help/
+[13] https://irssi.org/documentation/settings/
+[14] https://irssi.org/New-users/#about-scripts
+[15] https://scripts.irssi.org/
+[16] https://themes.irssi.org/

docs/capsicum.txt

@@ -0,0 +1,31 @@
+Capsicum is a lightweight OS capability and sandbox framework provided
+by FreeBSD.  When built with Capsicum support - which is the default under
+FreeBSD - Irssi can enter a Capsicum capability mode (a sandbox), greatly
+limiting possible consequences of a potential security hole in Irssi
+or the libraries it depends on.
+
+To make Irssi enter capability mode on startup, add
+
+capsicum = "yes";
+awaylog_file = "~/irclogs/away.log";
+
+to your ~/.irssi/config in the settings/core section, and restart the
+client.  Alternatively you can enter it "by hand", using the
+"/capsicum enter" command.  From the security point of view it's strongly
+preferable to use the former method, to avoid establishing connections
+without the sandbox protection; the "/capsicum" command is only intended
+for experimentation, and in cases where you need to do something that's not
+possible in capability mode - run scripts, for example - before continuing.
+
+There is no way to leave the capability mode, apart from exiting Irssi.
+When running in capability mode, there are certain restrictions - Irssi
+won't be able to access any files outside the directory pointed to by
+capsicum_irclogs_path (which defaults to ~/irclogs/).  If you change
+the path when already in capability mode it won't be effective until
+you restart Irssi.  Capability mode also makes it impossible to use
+the "/save" command.
+
+Currently there is no way to use custom SSL certificates.  As a workaround
+you can establish connections and enter the capability mode afterwards
+using the "/capsicum enter" command.
+

docs/crash.txt

@@ -1,9 +1,11 @@
 How to submit a good bug report?
 
-Send them to bug reporting system in http://bugs.irssi.org/
+Bugs are tracked via the GitHub issue tracker. Open an issue at:
+https://github.com/irssi/irssi/issues
 
 First you should give the following information:
- - irssi version, if CVS (or devel. tarball) then which day?
+ - irssi version, if git (or devel. tarball) then which commit hash (or date
+   from /version)?
  - operating system / distribution and it's version
  - when did it crash? did you do something? can you reproduce the crash?
 

docs/design.html

@@ -0,0 +1,165 @@
+<base href='https://irssi.org/documentation/design/'>
+<h1>Design</h1>
+    <p>Irssi’s hierarchy is something like this:</p>
+
+<pre class="repl" id="fig1"><code class="language-ascidia">
+        sub1 sub2
+           \ /
+      xxx  IRC       COMMON ICQ  yyy
+       |    |           |    |    |
+       '----+-----:-----+----+----'
+                  |
+                 GUI (gtk/gnome, qt/kde, text, none)
+                  |
+        sub1 sub2 |
+           \ /    |
+      xxx  IRC    |  COMMON ICQ  yyy
+       '----+-----+-----+----+----'
+                  |
+              COMMON UI
+                  |
+        sub1 sub2 |
+           \ /    |
+      xxx  IRC    |    ICQ  yyy
+       |    |     |     |    |
+       '----+-----+-----+----'
+                  |
+                CORE
+                /
+       lib-config
+
+</code></pre>
+
+<p>(IRC, ICQ, xxx and yyy are chat protocols ..)</p>
+
+<p>(sub1 and sub2 are submodules of IRC module, like DCC and flood protect)</p>
+
+<p>Chat protocols and frontends are kept in separate modules. Common UI
+and GUI modules also have the common parts which don’t know anything
+about the chat protocols. This should allow implementing modules to
+whatever chat protocols and with whatever frontends easily.</p>
+
+<h2 id="signals">Signals</h2>
+
+<p>Communication between different modules are done with “signals”. They are
+not related to UNIX signals in any way, you could more like think of them
+as “events” - which might be a better name for them, but I don’t really
+want to change it anymore :)</p>
+
+<p>So, you send signal with <code>signal_emit()</code> and it’s sent to all modules that
+have grabbed it by calling <code>signal_add()</code> in their init function. For
+example:</p>
+
+<div><div><pre><code>signal_emit("mysignal", 1, "hello");
+</code></pre></div></div>
+
+<p>Sends a “mysignal” function with one argument “hello” - before that, you
+should have grabbed the signal somewhere else with:</p>
+
+<div><div><pre><code>static void sig_mysignal(const char *arg1)
+{
+  /* arg1 contains "hello" */
+}
+
+signal_add("mysignal", (SIGNAL_FUNC) sig_mysignal);
+</code></pre></div></div>
+
+<p>There are three different <code>signal_add()</code> functions which you can use to
+specify if you want to grab the signal first, “normally” or last. You can
+also stop the signal from going any further.</p>
+
+<p>Emitting signal with it’s name creates a small overhead since it has to
+look up the signal’s numeric ID first, after which it looks up the signal
+structure. This is done because if you call a signal <em>really</em> often,
+it’s faster to find it with it’s numeric ID instead of the string. You
+can use <code>signal_get_uniq_id()</code> macro to convert the signal name into ID -
+you’ll have to do this only once! - and use <code>signal_emit_id()</code> to emit the
+signal. Don’t bother to do this unless your signal is sent (or could be
+sent) several times in a second.</p>
+
+<p>See <code>src/core/signals.h</code> for definition of the signal function, and
+signals.txt for a list of signals.</p>
+
+<h2 id="lib-config">lib-config</h2>
+
+<p>Irssi depends on this for reading and saving configuration.
+(created by me for irssi)</p>
+
+<h2 id="core-module">CORE module</h2>
+
+<p>Provides some functionality that all other modules can use:</p>
+<ul>
+  <li>signal handling</li>
+  <li>keeping list of settings</li>
+  <li>keeping list of /commands</li>
+  <li>keeping track of loaded modules</li>
+  <li>networking functions (with nonblocking connects, IPv6 support)</li>
+  <li>handles connecting to servers</li>
+  <li>raw logging of server’s input/output data</li>
+  <li>/EVAL support</li>
+  <li>fgets() like function line_split() without any maximum line limits</li>
+  <li>command line parameter handling</li>
+  <li>miscellaneous useful little functions</li>
+  <li>handles logging</li>
+</ul>
+
+<h2 id="common-ui-module">COMMON UI module</h2>
+
+<ul>
+  <li>knows basics about windows and window items (=channels, queries, ..)</li>
+  <li>printtext() - parsing texts and feeding it for GUI to print.</li>
+  <li>themes</li>
+  <li>translation tables</li>
+  <li>text hilighting</li>
+  <li>command history</li>
+  <li>user interface (/commands) for CORE’s functionality</li>
+</ul>
+
+<h2 id="gui-modules">GUI modules</h2>
+
+<ul>
+  <li>all the rest of the functionality needed for a working client.</li>
+</ul>
+
+<h2 id="irc-module">IRC module</h2>
+
+<ul>
+  <li>CORE
+    <ul>
+      <li>IRC specific /commands</li>
+      <li>flood protecting commands sent to server</li>
+      <li>creating IRC masks based on nick/address for bans, ignores, etc.</li>
+      <li>keeps list of channels, nicks, channel modes, bans, etc.</li>
+      <li>keeps list of servers, server settings, irc networks,
+server reconnections and irc network splits</li>
+      <li>redirection of commands’ replies</li>
+      <li>lag detection</li>
+      <li>ctcp support and flood protection</li>
+      <li>Handles ignoring people</li>
+    </ul>
+  </li>
+  <li>DCC
+    <ul>
+      <li>DCC chat, send and get</li>
+    </ul>
+  </li>
+  <li>FLOOD
+    <ul>
+      <li>detects private or channel flooding and sends “flood” signal</li>
+      <li>automatic ignoring when flooding</li>
+    </ul>
+  </li>
+  <li>NOTIFYLIST
+    <ul>
+      <li>handles notifylist</li>
+    </ul>
+  </li>
+</ul>
+
+<h2 id="irc-ui-module">IRC UI module</h2>
+
+<ul>
+  <li>placing channels and queries in windows</li>
+  <li>nick completion</li>
+  <li>printing infomation of some events</li>
+</ul>

docs/design.txt

@@ -1,150 +1,139 @@
+Design
 
- Irssi's hierarchy is something like this:
+Irssi’s hierarchy is something like this:
+
+        sub1 sub2
+           \ /
+      xxx  IRC       COMMON ICQ  yyy
+       |    |           |    |    |
+       '----+-----:-----+----+----'
+                  |
+                 GUI (gtk/gnome, qt/kde, text, none)
+                  |
+        sub1 sub2 |
+           \ /    |
+      xxx  IRC    |  COMMON ICQ  yyy
+       '----+-----+-----+----+----'
+                  |
+              COMMON UI
+                  |
+        sub1 sub2 |
+           \ /    |
+      xxx  IRC    |    ICQ  yyy
+       |    |     |     |    |
+       '----+-----+-----+----'
+                  |
+                CORE
+                /
+       lib-config
 
 
-         sub1 sub2
-            \ /
-       xxx  IRC       COMMON ICQ  yyy
-        |____|___________|____|____|
-                   |
-                  GUI (gtk/gnome, qt/kde, text, none)
-                   |
-         sub1 sub2 |
-            \ /    |
-       xxx  IRC    |  COMMON ICQ  yyy
-        |____|_____|_____|____|____|
-                   |
-               COMMON UI
-                   |
-         sub1 sub2 |
-            \ /    |
-       xxx  IRC    |    ICQ  yyy
-        |____|_____|_____|____|
-                   |
-                 CORE
-                 /
-        lib-config
+(IRC, ICQ, xxx and yyy are chat protocols ..)
 
+(sub1 and sub2 are submodules of IRC module, like DCC and flood protect)
 
- (IRC, ICQ, xxx and yyy are chat protocols ..)
- (sub1 and sub2 are submodules of IRC module, like DCC and flood protect)
+Chat protocols and frontends are kept in separate modules. Common UI and GUI
+modules also have the common parts which don’t know anything about the chat
+protocols. This should allow implementing modules to whatever chat protocols
+and with whatever frontends easily.
 
+Signals
 
- Chat protocols and frontends are kept in separate modules. Common UI
- and GUI modules also have the common parts which don't know anything
- about the chat protocols. This should allow implementing modules to
- whatever chat protocols and with whatever frontends easily.
+Communication between different modules are done with “signals”. They are not
+related to UNIX signals in any way, you could more like think of them as
+“events” - which might be a better name for them, but I don’t really want to
+change it anymore :)
 
- ** Signals
+So, you send signal with signal_emit() and it’s sent to all modules that have
+grabbed it by calling signal_add() in their init function. For example:
 
- Communication between different modules are done with "signals". They are
- not related to UNIX signals in any way, you could more like think of them
- as "events" - which might be a better name for them, but I don't really
- want to change it anymore :)
+signal_emit("mysignal", 1, "hello");
 
- So, you send signal with signal_emit() and it's sent to all modules that
- have grabbed it by calling signal_add() in their init function. For
- example:
+Sends a “mysignal” function with one argument “hello” - before that, you should
+have grabbed the signal somewhere else with:
 
-   signal_emit("mysignal", 1, "hello");
+static void sig_mysignal(const char *arg1)
+{
+  /* arg1 contains "hello" */
+}
 
- Sends a "mysignal" function with one argument "hello" - before that, you
- should have grabbed the signal somewhere else with:
+signal_add("mysignal", (SIGNAL_FUNC) sig_mysignal);
 
-   static void sig_mysignal(const char *arg1)
-   {
-     /* arg1 contains "hello" */
-   }
+There are three different signal_add() functions which you can use to specify
+if you want to grab the signal first, “normally” or last. You can also stop the
+signal from going any further.
 
-   signal_add("mysignal", (SIGNAL_FUNC) sig_mysignal);
+Emitting signal with it’s name creates a small overhead since it has to look up
+the signal’s numeric ID first, after which it looks up the signal structure.
+This is done because if you call a signal really often, it’s faster to find it
+with it’s numeric ID instead of the string. You can use signal_get_uniq_id()
+macro to convert the signal name into ID - you’ll have to do this only once! -
+and use signal_emit_id() to emit the signal. Don’t bother to do this unless
+your signal is sent (or could be sent) several times in a second.
 
- There are three different signal_add() functions which you can use to
- specify if you want to grab the signal first, "normally" or last. You can
- also stop the signal from going any further.
+See src/core/signals.h for definition of the signal function, and signals.txt
+for a list of signals.
 
- Emitting signal with it's name creates a small overhead since it has to
- look up the signal's numeric ID first, after which it looks up the signal
- structure. This is done because if you call a signal _really_ often,
- it's faster to find it with it's numeric ID instead of the string. You
- can use signal_get_uniq_id() macro to convert the signal name into ID -
- you'll have to do this only once! - and use signal_emit_id() to emit the
- signal. Don't bother to do this unless your signal is sent (or could be
- sent) several times in a second.
+lib-config
 
- See src/core/signals.h for definition of the signal function, and
- signals.txt for a list of signals.
+Irssi depends on this for reading and saving configuration. (created by me for
+irssi)
 
+CORE module
 
- ** lib-config
+Provides some functionality that all other modules can use:
 
-   Irssi depends on this for reading and saving configuration.
-   (created by me for irssi)
+  • signal handling
+  • keeping list of settings
+  • keeping list of /commands
+  • keeping track of loaded modules
+  • networking functions (with nonblocking connects, IPv6 support)
+  • handles connecting to servers
+  • raw logging of server’s input/output data
+  • /EVAL support
+  • fgets() like function line_split() without any maximum line limits
+  • command line parameter handling
+  • miscellaneous useful little functions
+  • handles logging
 
+COMMON UI module
 
- ** CORE module
+  • knows basics about windows and window items (=channels, queries, ..)
+  • printtext() - parsing texts and feeding it for GUI to print.
+  • themes
+  • translation tables
+  • text hilighting
+  • command history
+  • user interface (/commands) for CORE’s functionality
 
- Provides some functionality that all other modules can use:
-   - signal handling
-   - keeping list of settings
-   - keeping list of /commands
-   - keeping track of loaded modules
-   - networking functions (with nonblocking connects, IPv6 support)
-   - handles connecting to servers
-   - raw logging of server's input/output data
-   - /EVAL support
-   - fgets() like function line_split() without any maximum line limits
-   - command line parameter handling
-   - miscellaneous useful little functions
-   - handles logging
+GUI modules
 
+  • all the rest of the functionality needed for a working client.
 
- ** COMMON UI module
+IRC module
 
-   - knows basics about windows and window items (=channels, queries, ..)
-   - printtext() - parsing texts and feeding it for GUI to print.
-   - themes
-   - translation tables
-   - text hilighting
-   - command history
-   - user interface (/commands) for CORE's functionality
+  • CORE
+      □ IRC specific /commands
+      □ flood protecting commands sent to server
+      □ creating IRC masks based on nick/address for bans, ignores, etc.
+      □ keeps list of channels, nicks, channel modes, bans, etc.
+      □ keeps list of servers, server settings, irc networks, server
+        reconnections and irc network splits
+      □ redirection of commands’ replies
+      □ lag detection
+      □ ctcp support and flood protection
+      □ Handles ignoring people
+  • DCC
+      □ DCC chat, send and get
+  • FLOOD
+      □ detects private or channel flooding and sends “flood” signal
+      □ automatic ignoring when flooding
+  • NOTIFYLIST
+      □ handles notifylist
 
+IRC UI module
 
- ** GUI modules
+  • placing channels and queries in windows
+  • nick completion
+  • printing infomation of some events
 
-   - all the rest of the functionality needed for a working client.
-
-
- ** IRC module
-
-   * CORE
-
-     - IRC specific /commands
-     - flood protecting commands sent to server
-     - creating IRC masks based on nick/address for bans, ignores, etc.
-     - keeps list of channels, nicks, channel modes, bans, etc.
-     - keeps list of servers, server settings, irc networks,
-       server reconnections and irc network splits
-     - redirection of commands' replies
-     - lag detection
-     - ctcp support and flood protection
-     - Handles ignoring people
-
-   * DCC
-
-     - DCC chat, send and get
-
-   * FLOOD
-
-     - detects private or channel flooding and sends "flood" signal
-     - automatic ignoring when flooding
-
-   * NOTIFYLIST
-
-     - handles notifylist
-
-
- ** IRC UI module
-
-   - placing channels and queries in windows
-   - nick completion
-   - printing infomation of some events

docs/example-cross-android-aarch64.txt

@@ -0,0 +1,47 @@
+[binaries]
+ar = 'aarch64-linux-android-ar'
+c = 'aarch64-linux-android-clang'
+cpp = 'aarch64-linux-android-clang++'
+ld = 'aarch64-linux-android-ld'
+pkgconfig = '/home/builder/.termux-build/_cache/android-r20-api-24-v3/bin/aarch64-linux-android-pkg-config'
+strip = 'aarch64-linux-android-strip'
+
+;; you have to substitute 5.30.2 with the Perl version, that can be
+;; obtained by running ` miniperl -e 'print substr $^V, 1' `
+
+perl = ['/home/builder/.termux-build/perl/src/miniperl', '-I/data/data/com.termux/files/usr/lib/perl5/5.30.2/aarch64-android', '-I/data/data/com.termux/files/usr/lib/perl5/5.30.2']
+
+[properties]
+needs_exe_wrapper = true
+c_args = ['-fstack-protector-strong', '-Oz', '-I/data/data/com.termux/files/usr/include']
+cpp_args = ['-fstack-protector-strong', '-Oz', '-I/data/data/com.termux/files/usr/include']
+c_link_args = ['-L/data/data/com.termux/files/usr/lib', '-Wl,-rpath=/data/data/com.termux/files/usr/lib', '-Wl,--enable-new-dtags', '-Wl,--as-needed', '-Wl,-z,relro,-z,now', '-landroid-glob']
+cpp_link_args = ['-L/data/data/com.termux/files/usr/lib', '-Wl,-rpath=/data/data/com.termux/files/usr/lib', '-Wl,--enable-new-dtags', '-Wl,--as-needed', '-Wl,-z,relro,-z,now', '-landroid-glob']
+
+;; if you do not have a cross-perl like miniperl available, you have
+;; to specify the required options by uncommenting the following
+;; properties
+
+;; you can get the proper values by running the commands on your
+;; Android device:
+
+;; ` perl -V::version: `
+; perl_version = '5.30.2'
+;; ` perl -MExtUtils::Embed -o ccopts `
+; perl_ccopts = ['-I/data/data/com.termux/files/usr/include', '-D_LARGEFILE_SOURCE', '-D_FILE_OFFSET_BITS=64', '-I/data/data/com.termux/files/usr/lib/perl5/5.30.2/aarch64-android/CORE']
+;; ` perl -MExtUtils::Embed -o ldopts `
+; perl_ldopts = ['-Wl,-E', '-I/data/data/com.termux/files/usr/include', '-L/data/data/com.termux/files/usr/lib/perl5/5.30.2/aarch64-android/CORE', '-lperl', '-lm', '-ldl']
+;; ` perl -V::archname: `
+; perl_archname = 'aarch64-android'
+;; ` perl -V::installsitearch: `
+; perl_installsitearch = '/data/data/com.termux/files/usr/lib/perl5/site_perl/5.30.2/aarch64-android'
+;; ` perl -V::installvendorarch: `
+; perl_installvendorarch = ''
+;; ` perl -E 'say for @INC' `
+; perl_inc = ['/data/data/com.termux/files/usr/lib/perl5/site_perl/5.30.2/aarch64-android', '/data/data/com.termux/files/usr/lib/perl5/site_perl/5.30.2', '/data/data/com.termux/files/usr/lib/perl5/5.30.2/aarch64-android', '/data/data/com.termux/files/usr/lib/perl5/5.30.2']
+
+[host_machine]
+cpu_family = 'arm'
+cpu = 'aarch64'
+endian = 'little'
+system = 'android'

docs/faq.html

@@ -1,152 +1,81 @@
-<h2>FAQ</h2>
+<base href='https://irssi.org/documentation/faq/'>
+<h1>Frequently Asked Questions</h1>
+    <h3 id="q-why-doesnt-irssi-display-colors-even-when-ircii-etc-displays-them">Q: Why doesn’t irssi display colors even when ircii etc. displays them?</h3>
 
-<h3>Q: Why doesn't irssi display colors even when ircii etc. displays them?</h3>
+<p>A: They force ANSI colors even if terminal doesn’t support them. By default, irssi uses colors only if terminfo/termcap so says. The correct way to fix this would be to change your TERM environment to a value where colors work, like xterm-256color or color_xterm (eg. <code>TERM=xterm-256color irssi</code>). If this doesn’t help, then use the evil way of <code>/SET term_force_colors ON</code>.</p>
 
-<p>A: They force ANSI colors even if terminal doesn't support them. By
-default, irssi uses colors only if terminfo/termcap so says. The correct
-way to fix this would be to change your TERM environment to a value where
-colors work, like xterm-color or color_xterm (eg. <code>TERM=xterm-color
-irssi</code>). If this doesn't help, then use the evil way of <code>/SET
-term_force_colors ON</code>.</p>
-
-
-<h3>Q: How do I easily write text to channel that starts with '/' character?</h3>
+<h3 id="q-how-do-i-easily-write-text-to-channel-that-starts-with--character">Q: How do I easily write text to channel that starts with ‘/’ character?</h3>
 
 <p>A: <code>/ /text</code></p>
 
+<h3 id="q-why-doesnt-irssi-update-my-realname-or-whatever-after-i-change-it-with-set-realname-and-reconnect-with-reconnect-or-server">Q: Why doesn’t irssi update my realname (or whatever) after I change it with <code>/SET realname</code> and reconnect with <code>/RECONNECT</code> or <code>/SERVER</code>?</h3>
 
-<h3>Q: Why doesn't irssi update my realname (or whatever) after I change it
-with <code>/SET realname</code> and reconnect with <code>/RECONNECT</code>
-or <code>/SERVER</code>?</h3>
+<p>A: Irssi is trying to be too smart. This will be fixed in future, but for now you should use <code>/DISCONNECT</code> and <code>/CONNECT</code>.</p>
 
-<p>A: Irssi is trying to be too smart. This will be fixed in future, but for
-now you should use <code>/DISCONNECT</code> and <code>/CONNECT</code>.</p>
+<h3 id="q-i-connected-to-some-server-which-isnt-responding-but-now-irssi-tries-to-connect-back-to-it-all-the-time-how-can-i-stop-it">Q: I connected to some server which isn’t responding but now irssi tries to connect back to it all the time! How can I stop it?</h3>
 
+<p>A: Two ways. The “good way” to do it is with <code>/DISCONNECT</code>. Check the server tags first with <code>/SERVER</code> without giving it any parameters, reconnections are those that have tag starting with “recon” text. So most probably you’re going to do <code>/DISCONNECT recon-1</code>. The other way is to remove all the reconnections with <code>/RMRECONNS</code>, easier but may remove some connections you actually wanted to reconnect (if you used multiple servers..).</p>
 
-<h3>Q: I connected to some server which isn't responding but now irssi tries
-to connect back to it all the time! How can I stop it?</h3>
+<h3 id="q-how-do-i-add-seconds-to-timestamp">Q: How do I add seconds to timestamp?</h3>
 
-<p>A: Two ways. The "good way" to do it is with <code>/DISCONNECT</code>.
-Check the server tags first with <code>/SERVER</code> without giving it any
-parameters, reconnections are those that have tag starting with "recon"
-text. So most probably you're going to do <code>/DISCONNECT recon-1</code>.
-The other way is to remove all the reconnections with
-<code>/RMRECONNS</code>, easier but may remove some connections you actually
-wanted to reconnect (if you used multiple servers..).</p>
+<p>A: <code>/FORMAT timestamp {timestamp %%H:%%M:%%S}</code> - and remember to add the trailing space :)</p>
 
+<h3 id="q-why-does-irssi-say-irssi-channel-not-fully-synchronized-yet-try-again-after-a-while-when-i-try-to-use-ban-etc">Q: Why does irssi say “Irssi: Channel not fully synchronized yet, try again after a while” when I try to use /BAN etc?</h3>
 
-<h3>Q: How do I add seconds to timestamp?</h3>
+<p>A: Possibly a bug in irssi, or ircd you’re using does something that irssi didn’t really notice. The new code should make this happen far less often than before, but one known reason for this is when irssi doesn’t notice that you were unable to join some channel. Currently however I don’t know of any such events irssi doesn’t know about.</p>
 
-<p>A: <code>/FORMAT timestamp {timestamp %%H:%%M:%%S}</code> - and remember
-to add the trailing space :)</p>
-
-
-<h3>Q: Why does irssi say "Irssi: Channel not fully synchronized yet, try
-again after a while" when I try to use /BAN etc?</h3>
- 
-<p>A: Possibly a bug in irssi, or ircd you're using does something that
-irssi didn't really notice. The new code should make this happen far less
-often than before, but one known reason for this is when irssi doesn't
-notice that you were unable to join some channel. Currently however I don't
-know of any such events irssi doesn't know about.</p>
-
-<p>Anyway, if this does happen, do <code>/RAWLOG SAVE ~/rawlog</code> soon
-after joining to channel, and either try to figure out yourself why irssi
-didn't get reply to WHO request, or send the whole log to cras@irssi.org. Note
-that the rawlog is by default only 200 lines and it may not be enough to
-show all needed information, so you might want to do <code>/SET rawlog_lines
-1000</code> or so.</p>
+<p>Anyway, if this does happen, do <code>/RAWLOG SAVE ~/rawlog</code> soon after joining to channel, and either try to figure out yourself why irssi didn’t get reply to WHO request, or open a Github issue with the full log included. Note that the rawlog is by default only 200 lines and it may not be enough to show all needed information, so you might want to do <code>/SET rawlog_lines 1000</code> or so.</p>
 
 <p><code>MODE +b</code> still works fine though.</p>
 
+<h3 id="q-wheres-the-gui-version">Q: Where’s the GUI version?</h3>
 
-<h3>Q: Where's the GUI version?</h3>
+<p>A: There was one on <a href="https://github.com/irssi-import/xirssi">irssi-import/xirssi</a> but it has not been maintained for a long time.</p>
 
-<p>A: Read
-<a href="http://www.irssi.org/about">http://www.irssi.org/about</a></p>
+<h3 id="q-how-do-i-autorejoin-channels-after-being-kicked">Q: How do I autorejoin channels after being kicked?</h3>
 
+<p>A: That’s evil and you shouldn’t do it. If you get kicked, you should stay out, at least until the channel forgot you existed :) Most channels I’ve joined just ban you if you autorejoin after kick. If you’re joined to channels who kick people for fun, try changing channels or something.</p>
 
-<h3>Q: How do I autorejoin channels after being kicked?</h3>
+<p>Anyway, if you REALLY want to do that, and you understand that you’re doing evilness, you can use the autorejoin.pl script that comes with irssi. You’ll still need to specify the channels you wish to rejoin with <code>/SET autorejoin_channels #chan1 #chan2 ...</code></p>
 
-<p>A: That's evil and you shouldn't do it. If you get kicked, you should stay
-out, at least until the channel forgot you existed :) Most channels I've
-joined just ban you if you autorejoin after kick. If you're joined to
-channels who kick people for fun, try changing channels or something.</p>
+<h3 id="q-how-do-i-announce-that-im-awayback-in-all-channels-ive-joined-or-how-do-i-change-my-nick-when-setting-myself-awayback">Q: How do I announce that I’m away/back in all channels I’ve joined? Or how do I change my nick when setting myself away/back?</h3>
 
-<p>Anyway, if you REALLY want to do that, and you understand that you're doing
-evilness, you can use the autorejoin.pl script that comes with irssi. You'll
-still need to specify the channels you wish to rejoin with <code>/SET
-autorejoin_channels #chan1 #chan2 ...</code></p>
+<p>A: That’s even worse than autorejoin. Who could possibly care every time you come and go? Many channels will kick you for using this, and I for example have added several ignores so I’d never need to see these messages. Learn to use <code>/AWAY</code> command properly and tell its existence to people who don’t know about it. <code>/WII yournick</code> shows your away reason much better for people who actually want to know if you’re there or not.</p>
 
+<h3 id="q-why-does-irssi-autojoin-on-invite-by-default">Q: Why does irssi autojoin on invite by default?</h3>
 
-<h3>Q: How do I announce that I'm away/back in all channels I've joined? Or
-how do I change my nick when setting myself away/back?</h3>
+<p>A: The setting is /SET join_auto_chans_on_invite - it’s not the same as regular autojoin-on-invite, which irssi doesn’t even have. The only channels that are joined on invite, are the ones you’ve added to config with /CHANNEL ADD -auto. This is very useful with +i channels when you need to first send an invite request to bot, or if you get accidentally kicked from channel, the kicker can invite you back immediately.</p>
 
-<p>A: That's even worse than autorejoin. Who could possibly care every time 
-you come and go? Many channels will kick you for using this, and I for example
-have added several ignores so I'd never need to see these messages. Learn to
-use <code>/AWAY</code> command properly and tell its existence to people
-who don't know about it. <code>/WII yournick</code> shows your away reason
-much better for people who actually want to know if you're there or not.</p>
+<p>I don’t see any bad side effects with this feature, so it’s ON by default. I guess someone could start kicking/inviting you all the time but server connection shouldn’t drop because of that, and you shouldn’t join channels whose operators are that evil.</p>
 
+<h3 id="q-how-to-make-utf-8-support-work-with-irssi">Q: How to make UTF-8 support work with irssi?</h3>
 
-<h3>Q: Why does irssi autojoin on invite by default?</h3>
+<p>A: Make sure your terminal supports UTF-8 (for example, <code>xterm -u8</code>). If you use screen, you may have to do <code>screen -U</code>. And in Irssi do <code>/SET term_charset utf-8</code>. (for 0.8.9 and older: <code>/SET term_type utf-8</code>)</p>
 
-<p>A: The setting is /SET join_auto_chans_on_invite - it's not the same
-as regular autojoin-on-invite, which irssi doesn't even have. The only
-channels that are joined on invite, are the ones you've added to config
-with /CHANNEL ADD -auto. This is very useful with +i channels when you
-need to first send an invite request to bot, or if you get accidentally
-kicked from channel, the kicker can invite you back immediately.</p>
+<h3 id="q-will-there-be-detach-like-feature">Q: Will there be /DETACH-like feature?</h3>
 
-<p>I don't see any bad side effects with this feature, so it's ON by
-default. I guess someone could start kicking/inviting you all the time
-but server connection shouldn't drop because of that, and you shouldn't
-join channels whose operators are that evil.</p>
+<p>A: <a href="https://tmux.github.io/">tmux</a>, <a href="https://www.gnu.org/software/screen/screen.html">screen</a> and <a href="https://sourceforge.net/projects/dtach/">dtach</a> can be used to do it just fine.</p>
 
+<h3 id="q-how-do-i-run-scripts-automatically-at-startup">Q: How do I run scripts automatically at startup?</h3>
 
-<h3>Q: How to make UTF-8 support work with irssi?</h3>
+<p>A: Put them into <code>~/.irssi/scripts/autorun/</code> directory. Or better would be if you placed them in <code>~/.irssi/scripts/</code> and created symlinks to autorun directory (eg. <code>cd ~/.irssi/scripts/autorun/ ; ln -s ../script.pl .</code>)</p>
 
-<p>A: Make sure your terminal supports UTF-8 (for example, <code>xterm -u8</code>).
-If you use screen, you may have to do <code>screen -U</code>. And in Irssi do
-<code>/SET term_charset utf-8</code>. (for 0.8.9 and older: <code>/SET term_type utf-8</code>)</p>
+<h3 id="q-how-do-i-execute-commands-automatically-at-startup">Q: How do I execute commands automatically at startup?</h3>
 
+<p>A: Put them into <code>~/.irssi/startup</code> file, each command on its own line. The preceding slash (/) is not necessary.</p>
 
-<h3>Q: Will there be /DETACH-like feature?</h3>
+<h3 id="q-how-do-i-easily-edit-existing-topic">Q: How do I easily edit existing topic?</h3>
 
-<p>A: Maybe. Detach code already is there, attach is just missing :) But I
-don't have much interest in coding it,
-<a href="http://www.gnu.org/software/screen/screen.html">screen</a> and
-<a href="http://dtach.sf.net/">dtach</a> can be used to do it just fine.</p>
+<p>A: <code>/TOPIC &lt;tab&gt;</code></p>
 
+<h3 id="q-how-can-i-have-whois-replies-to-active-window">Q: How can I have /WHOIS replies to active window?</h3>
 
-<h3>Q: How do I run scripts automatically at startup?</h3>
+<p>A: You can disable the status window, or do <code>/WINDOW LEVEL -CRAP</code> in it which would also make several other messages show up in active window. You can also use a <a href="https://dgl.cx/irssi/hack-whois-in-current-window.pl">script</a>.</p>
 
-<p>A: Put them into <code>~/.irssi/scripts/autorun/</code> directory. Or
-better would be if you placed them in <code>~/.irssi/scripts/</code> and
-created symlinks to autorun directory (eg. <code>cd
-~/.irssi/scripts/autorun/ ; ln -s ../script.pl .</code>)</p>
+<h3 id="q-how-do-i-add-the-active-network-to-the-statusbar">Q: How do I add the active network to the statusbar</h3>
 
+<p>A: Modify the window-line in statusbar section in config file to <code>window = "{sb $winref:$tag/$T{sbmode $M}}";</code></p>
 
-<h3>Q: How do I execute commands automatically at startup?</h3>
-
-<p>A: Put them into <code>~/.irssi/startup</code> file, each command on its
-own line. The preceding slash (/) is not necessary.</p>
-
-
-<h3>Q: How do I easily edit existing topic?</h3>
-
-<p>A: /TOPIC &lt;tab&gt;</p>
-
-<h3>Q: How can I have /WHOIS replies to active window?</h3>
-
-<p>A: You can disable the status window, or do <code>/WINDOW LEVEL
--CRAP</code> in it which would also make several other messages show up in
-active window. You can also use a
-<a href="http://dgl.cx/irssi/hack-whois-in-current-window.pl">script</a>.</p>
-
-<h3>Q: How do I add the active network to the statusbar</h3>
-
-<p>A: Modify the window-line in statusbar section in config file to
-<code>window = "{sb $winref:$tag/$T{sbmode $M}}";</code></p>
+<h3 id="q-how-to-pronounce-irssi">Q: How to pronounce Irssi?</h3>
 
+<p>A: Check <a href="/assets/irssi.wav">here</a></p>

docs/faq.txt

@@ -0,0 +1,124 @@
+   Frequently Asked Questions
+
+Q: Why doesn’t irssi display colors even when ircii etc. displays them?
+A: They force ANSI colors even if terminal doesn’t support them. By default,
+   irssi uses colors only if terminfo/termcap so says. The correct way to fix this
+   would be to change your TERM environment to a value where colors work, like
+   xterm-256color or color_xterm (eg. TERM=xterm-256color irssi). If this doesn’t
+   help, then use the evil way of /SET term_force_colors ON.
+
+Q: How do I easily write text to channel that starts with ‘/’ character?
+A: / /text
+
+Q: Why doesn’t irssi update my realname (or whatever) after I change it with /
+   SET realname and reconnect with /RECONNECT or /SERVER?
+A: Irssi is trying to be too smart. This will be fixed in future, but for now
+   you should use /DISCONNECT and /CONNECT.
+
+Q: I connected to some server which isn’t responding but now irssi tries to
+   connect back to it all the time! How can I stop it?
+A: Two ways. The “good way” to do it is with /DISCONNECT. Check the server tags
+   first with /SERVER without giving it any parameters, reconnections are those
+   that have tag starting with “recon” text. So most probably you’re going to do /
+   DISCONNECT recon-1. The other way is to remove all the reconnections with /
+   RMRECONNS, easier but may remove some connections you actually wanted to
+   reconnect (if you used multiple servers..).
+
+Q: How do I add seconds to timestamp?
+A: /FORMAT timestamp {timestamp %%H:%%M:%%S} - and remember to add the trailing
+   space :)
+
+Q: Why does irssi say “Irssi: Channel not fully synchronized yet, try again
+   after a while” when I try to use /BAN etc?
+A: Possibly a bug in irssi, or ircd you’re using does something that irssi
+   didn’t really notice. The new code should make this happen far less often than
+   before, but one known reason for this is when irssi doesn’t notice that you
+   were unable to join some channel. Currently however I don’t know of any such
+   events irssi doesn’t know about.
+
+   Anyway, if this does happen, do /RAWLOG SAVE ~/rawlog soon after joining to
+   channel, and either try to figure out yourself why irssi didn’t get reply to
+   WHO request, or open a Github issue with the full log included. Note that the
+   rawlog is by default only 200 lines and it may not be enough to show all needed
+   information, so you might want to do /SET rawlog_lines 1000 or so.
+
+   MODE +b still works fine though.
+
+Q: Where’s the GUI version?
+A: There was one on [1]irssi-import/xirssi but it has not been maintained for a
+   long time.
+
+Q: How do I autorejoin channels after being kicked?
+A: That’s evil and you shouldn’t do it. If you get kicked, you should stay out,
+   at least until the channel forgot you existed :) Most channels I’ve joined just
+   ban you if you autorejoin after kick. If you’re joined to channels who kick
+   people for fun, try changing channels or something.
+
+   Anyway, if you REALLY want to do that, and you understand that you’re doing
+   evilness, you can use the autorejoin.pl script that comes with irssi. You’ll
+   still need to specify the channels you wish to rejoin with /SET
+   autorejoin_channels #chan1 #chan2 ...
+
+Q: How do I announce that I’m away/back in all channels I’ve joined? Or how do
+   I change my nick when setting myself away/back?
+A: That’s even worse than autorejoin. Who could possibly care every time you
+   come and go? Many channels will kick you for using this, and I for example have
+   added several ignores so I’d never need to see these messages. Learn to use /
+   AWAY command properly and tell its existence to people who don’t know about it.
+   /WII yournick shows your away reason much better for people who actually want
+   to know if you’re there or not.
+
+Q: Why does irssi autojoin on invite by default?
+A: The setting is /SET join_auto_chans_on_invite - it’s not the same as regular
+   autojoin-on-invite, which irssi doesn’t even have. The only channels that are
+   joined on invite, are the ones you’ve added to config with /CHANNEL ADD -auto.
+   This is very useful with +i channels when you need to first send an invite
+   request to bot, or if you get accidentally kicked from channel, the kicker can
+   invite you back immediately.
+
+   I don’t see any bad side effects with this feature, so it’s ON by default. I
+   guess someone could start kicking/inviting you all the time but server
+   connection shouldn’t drop because of that, and you shouldn’t join channels
+   whose operators are that evil.
+
+Q: How to make UTF-8 support work with irssi?
+A: Make sure your terminal supports UTF-8 (for example, xterm -u8). If you use
+   screen, you may have to do screen -U. And in Irssi do /SET term_charset utf-8.
+   (for 0.8.9 and older: /SET term_type utf-8)
+
+Q: Will there be /DETACH-like feature?
+A: [2]tmux, [3]screen and [4]dtach can be used to do it just fine.
+
+Q: How do I run scripts automatically at startup?
+A: Put them into ~/.irssi/scripts/autorun/ directory. Or better would be if you
+   placed them in ~/.irssi/scripts/ and created symlinks to autorun directory (eg.
+   cd ~/.irssi/scripts/autorun/ ; ln -s ../script.pl .)
+
+Q: How do I execute commands automatically at startup?
+A: Put them into ~/.irssi/startup file, each command on its own line. The
+   preceding slash (/) is not necessary.
+
+Q: How do I easily edit existing topic?
+A: /TOPIC <tab>
+
+Q: How can I have /WHOIS replies to active window?
+A: You can disable the status window, or do /WINDOW LEVEL -CRAP in it which
+   would also make several other messages show up in active window. You can also
+   use a [5]script.
+
+Q: How do I add the active network to the statusbar
+A: Modify the window-line in statusbar section in config file to window = "{sb
+   $winref:$tag/$T{sbmode $M}}";
+
+Q: How to pronounce Irssi?
+A: Check [6]here
+
+
+   References:
+
+   [1] https://github.com/irssi-import/xirssi
+   [2] https://tmux.github.io/
+   [3] https://www.gnu.org/software/screen/screen.html
+   [4] https://sourceforge.net/projects/dtach/
+   [5] https://dgl.cx/irssi/hack-whois-in-current-window.pl
+   [6] https://irssi.org/assets/irssi.wav

docs/formats.txt

@@ -23,10 +23,13 @@
    %U                      Underline on/off
    %8                      Reverse on/off
    %9      %_              Bold on/off
+   %I                      Italic on/off
    %:                      Insert newline
    %|                      Marks the indentation position
    %#                      Monospace font on/off (useful with lists and GUI)
    %%                      A single %
+   %XAB            %xAB    Color from extended plane (A=1-7, B=0-Z)
+   %ZAABBCC    %zAABBCC    HTML color (in hex notation)
 
  In .theme files %n works a bit differently. See default.theme
  for more information.

docs/help/Makefile.am.gen

@@ -1,12 +0,0 @@
-# Makefile.am is autogenerated by autogen.sh from Makefile.am.gen
-
-helpdir = $(datadir)/irssi/help
-
-help_DATA = \
-@HELPFILES@
-
-EXTRA_DIST = \
-	Makefile.am.gen \
-	$(help_DATA)
-
-SUBDIRS = in

docs/help/in/Makefile.am.gen

@@ -1,5 +0,0 @@
-# Makefile.am is autogenerated by autogen.sh from Makefile.am.gen
-
-EXTRA_DIST = \
-	Makefile.am.gen \
-@HELPFILES@

docs/help/in/accept.in

@@ -1,28 +1,30 @@
 
+%9Syntax:%9
+
 @SYNTAX:accept@
-MODE <your nick> <+|->g
 
-Works only in some IRC networks.
+%9Parameters:%9
 
-ACCEPT allows you to specify who you want to receive private messages
-and notices from while you are in callerid (+g) mode.
-When you have user mode +g enabled, messages from other users are blocked and
-the sender is notified; you are also notified but at most once per minute.
-IRC operators and services can usually send through +g.
+    A comma-separated list of nicknames to add or remove; if no argument is
+    given, your accept list will be displayed.
 
-The accept list is lost when you disconnect.
-Users are automatically removed from the accept list if they quit, split
-or change nick.
+%9Description:%9
 
-The argument is a comma-separated list of nicks to add or (when prefixed
-with a '-') to remove. No output is returned for users successfully added
-or removed.
-If no arguments are given, your accept list is displayed (ACCEPT * on the
-protocol level). 
+    Allows you to specify who you want to receive private messages and notices
+    from while you have callerid enabled.
 
-Example:
-    /ACCEPT user1,user2,-user3,-user4  - Adds user1 and user2 and removes
-                                         user3 and user4.
- 
-See also: IGNORE, SILENCE
+    When you have callerid enabled, messages from other users are blocked and
+    the sender is notified.
+
+    Users are automatically removed from the accept list if they quit, split
+    or change nickname; the accept list is lost when you disconnect.
+
+    This command only works on IRC servers that support the callerid user mode.
+
+%9Examples:%9
+
+    /ACCEPT mike,bob,-john,-sarah
+    /ACCEPT sarah,-bob
+
+%9See also:%9 IGNORE, SILENCE
 

docs/help/in/action.in

@@ -1,9 +1,23 @@
 
+%9Syntax:%9
+
 @SYNTAX:action@
 
-Same as ME, but gets channel or nick as an additional parameter.
-Example: /ACTION #irssi yawns
-(This outputs the following to #irssi: * Nick yawns)
+%9Parameters:%9
 
-See also: ME
+    -<server tag>:    The server tag you want to send the action emote to.
+
+    A target nickname or channel and the message to emote.
+
+%9Description:%9
+
+    Sends an action emote to a nickname or a channel.
+
+%9Examples:%9
+
+    /ACTION #irssi is hungry!
+    /ACTION mike had an awesome day @ work
+    /ACTION -efnet #irssi is happy it's Friday
+
+%9See also:%9 ME
 

docs/help/in/admin.in

@@ -1,8 +1,22 @@
 
+%9Syntax:%9
+
 @SYNTAX:admin@
 
-Displays the administrative details about the given server. If
-no server is specified, the server you are connected to is
-used. If a nickname is supplied then it gives the administrative 
-information for that person's current server.
+%9Parameters:%9
+
+    A nickname or server for which you want to know the administrative details;
+    if no argument is given, the server you are connected to will be used.
+
+%9Description:%9
+
+    Displays the administrative details of a server.
+
+%9Examples:%9
+
+    /ADMIN
+    /ADMIN irc.libera.chat
+    /ADMIN mike
+
+%9See also:%9 INFO
 

docs/help/in/alias.in

@@ -1,22 +1,37 @@
 
+%9Syntax:%9
+
 @SYNTAX:alias@
 
-Creates a new alias or shows matching defined aliases. Without
-parameters shows all defined aliases. Multiple commands can be run if
-separated with ';' character. Parameters given to alias are in $0..$9
-variables, if you don't use them in your alias, all parameters are
-automatically appended after it.
+%9Parameters:%9
 
-Examples:
+    A name of the alias and the command to execute. You can prepend the alias
+    with the '-' character to remove the alias; if no argument is given, your
+    aliases will be displayed.
 
-/ALIAS w
-   - shows all defined aliases starting with letter w.
+%9Description:%9
 
-/ALIAS send echo Sending file $1 to $0;dcc send $0-
-   - creates alias 'send'.
+    Creates or updates an alias; you can use the ';' character to separate
+    multiple commands.
 
-/ALIAS -send
-   - removes alias 'send'.
+    The parameters given to the alias are expanded in '$[\d]'; for example $0,
+    $1, $2, $8, ..., as well as any other special variable.
 
-See also: UNALIAS
+    If you don't use any parameters in your alias, all parameters will be
+    automatically appended after it.
+
+%9Examples:%9
+
+    /ALIAS
+    /ALIAS UH USERHOST
+    /ALIAS COMEBACK SAY I was hoping for a battle of wits, but you seem to be unarmed.
+    /ALIAS -COMEBACK
+    /ALIAS UNACT SCRIPT EXEC \$_->activity(0) for Irssi::windows
+    /ALIAS QOP ^MSG Q op $C
+
+%9References:%9
+
+    https://github.com/irssi/irssi/blob/master/docs/special_vars.txt
+
+%9See also:%9 BIND, UNALIAS
 

docs/help/in/away.in

@@ -1,28 +1,33 @@
 
+%9Syntax:%9
+
 @SYNTAX:away@
 
-   -one 
-   -all
+%9Parameters:%9
 
-This command marks you as being "away". It is used to tell people that 
-you currently aren't paying attention to your screen. You might use it 
-if you are taking a nap, in the shower, getting some food, or otherwise 
-just aren't there at the moment. When you're "away" you will see "(zZzZ)"
-in your statusbar.
+   -one:    Marks yourself as away on the active server.
+   -all:    Marks yourself as away on all the servers you are connected to.
 
-Anyone who does a WHOIS on your nickname will see that you are away, 
-as well as your away message. Anyone doing a WHO that returns information 
-about you will also see that you're gone. 
+   Your away message; if no argument is given, your away status will be removed.
 
-By default, if someone sends you a MSG while you are away, your client 
-will beep. You can turn this off by setting BEEP_WHEN_AWAY to OFF. 
+%9Description:%9
 
-If you send a MSG to someone who is away, you will automatically be 
-notified of this. By default, you will only receive this notification 
-once. If you wish to see it every time (to tell when a person is no 
-longer marked away, for instance), change SHOW_AWAY_ONCE to OFF. 
+    Marks yourself as 'away'; this method is used to inform people that you
+    are not paying attention to your screen.
 
-You can remove your away status by using AWAY with no arguments. 
+    You might use it when you are taking a nap, in the shower, getting some
+    food, or otherwise engaged. When you're 'away' you will see '(zZzZ)' in
+    your statusbar.
 
-See also: SET AWAY
+    Anyone who does a WHOIS on your nickname will see that you are away, as
+    well as your away message.
+
+%9Examples:%9
+
+    /AWAY
+    /AWAY I'm getting some food.
+    /AWAY zZzZ
+    /AWAY -one Feeding the cat!
+
+%9See also:%9 DISCONNECT
 

docs/help/in/ban.in

@@ -1,27 +1,42 @@
 
+%9Syntax:%9
+
 @SYNTAX:ban@
 
-Bans the specified nick or userhost mask.
+%9Parameters:%9
 
-If nick is given as parameter, the ban type is used to generate the ban
-mask. /SET ban_type specified the default ban type. Ban type is one of
-the following:
+    -normal:    Uses the *!*user@*.domain.tld format.
+    -user:      Uses the *!*user@* format.
+    -host:      Uses the *!*@host.domain.tld format.
+    -domain:    Uses the *!*@*.domain.tld format.
+    -custom:    Uses the custom format.
 
-    Normal - *!*user@*.domain.net
-    User   - *!*user@*
-    Host   - *!*@host.domain.net
-    Domain - *!*@*.domain.net
-    Custom [nick] [user] [host] [domain]
+    A channel and the nicknames or hostnames to ban; if no arguments are given
+    the bans in the active channel are displayed.
 
-If no arguments are given the current bans in this channel are displayed.
+    If no ban format parameter is given, the value of the ban_type setting will
+    be used to generate the hostmask to ban.
 
-Examples:
-    /BAN loser        - Bans the nick 'loser'
-    /BAN -host loser  - Bans the host of nick 'loser'
-    /BAN *!*@*.org    - Bans all the users coming from any .org domain.
+%9Description:%9
 
-    /SET ban_type custom nick domain - nick!*@*.domain.net
-    /SET ban_type custom user host   - *!user@host.domain.net
+    Adds one or more bans to a channel.
 
-See also: KNOCKOUT, KICKBAN
+%9Configuring the custom format:%9
+
+    You must set the custom ban_type to the format you would like to use. For
+    example, if you set the custom ban_type to 'nick domain', it will generate
+    a ban based on the nick!*@*.domain.tld format.
+
+%9Examples:%9
+
+    /BAN
+    /BAN mike
+    /BAN -host bob
+    /BAN *!*@*.irssi.org
+    /BAN -domain sarah
+
+    /SET ban_type custom nick domain
+    /SET ban_type custom user host
+
+%9See also:%9 DEOP, KICKBAN, KNOCKOUT, OP, UNBAN
 

docs/help/in/beep.in

@@ -1,6 +1,15 @@
 
+%9Syntax:%9
+
 @SYNTAX:beep@
 
-Outputs the bell-character, usually causing
-your terminal beep.
+%9Description:%9
+
+    Outputs the bell-character, usually causing your terminal to beep.
+
+%9Examples:%9
+
+    /BEEP
+
+%9See also:%9 CLEAR
 

docs/help/in/bind.in

@@ -1,48 +1,37 @@
 
+%9Syntax:%9
+
 @SYNTAX:bind@
 
-Bind some action to specified keystroke. Remember that all characters
-in keystrokes are case-sensitive! Uppercase letter usually means that
-you need to keep SHIFT pressed to get the key to work.
+%9Parameters:%9
 
-Most most commonly used keystrokes are:
+    -list:      Displays a list of all the bindable commands.
+    -delete:    Removes the binding.
+    -reset:     Reset a key to its default binding.
 
- ^X - Ctrl-X
- meta-x - Meta-x (Meta is quite often Alt-key in PCs, ESC-x works too)
+    A name of the binding and the command to perform; if no parameter is given,
+    the list of bindings will be displayed.
 
-Irssi has by default also defined several other keys which you can use:
+Details:
 
- return                  - The return/enter key
- space, backspace        - Space / backspace
- up, down, left, right   - Arrow keys
- cleft, cright           - Ctrl-left/right
- home, end, prior, next  - prior = Page Up, next = Page Down
- insert, delete
+    Adds or removes a binding; the binding itself is case-sensitive and may
+    contain as many characters as you want.
 
-The keystroke can contain as many key presses as you want, and you can
-define names for different key sequences to use them more easily (the
-keys above are done like that). For example, you may want to manage
-windows with ^W key, so that ^W^C creates new window, ^W^K kills the
-active window, etc. you may do it like:
+    Key bindings are case sensitive so uppercase letters mean you also have
+    to use the shift key, except for ctrl which does not support shift but
+    the keys must always be typed in uppercase.
 
- /BIND ^W^C /WINDOW NEW HIDE
- /BIND ^W^K /WINDOW KILL
+%9Examples:%9
 
-But maybe you wish to give these binds to other people who want to use
-some other key than ^W, then it would be better done as:
+    /BIND
+    /BIND meta-c /CLEAR
+    /BIND meta-C /CYCLE
+    /BIND meta-q change_window 16
+    /BIND -delete meta-y
+    /BIND ^W^C /WINDOW NEW HIDE
+    /BIND ^W^K /WINDOW KILL
+    /BIND ^[[11~ command AWAY I'm off for today :)
+    /BIND ^[[12~ command AWAY
 
- /BIND ^W key window
- /BIND window-^C /WINDOW NEW HIDE
- /BIND window-^K /WINDOW KILL
+%9See also:%9 ALIAS
 
-
-To get a list of all bindable commands use /bind -list.
-
-Examples:
-
-Clear screen:
-  /BIND meta-c /CLEAR
-
-People with qwertz layout probably want to swap meta-y and meta-z:
-  /BIND meta-z change_window 16
-  /BIND -delete meta-y

docs/help/in/cat.in

@@ -1,8 +1,28 @@
 
+%9Syntax:%9
+
 @SYNTAX:cat@
 
-Outputs the contents of the specified file. Equivalent to
-UNIX 'cat' command.
+%9Parameters:%9
 
-See also: CD
+    -window:            Displays the output in the active window.
+
+    The file to display and optionally a position to seek in the file,
+    in bytes.
+
+%9Description:%9
+
+    Displays the contents of the specified file in the active window if -window
+    is specified, otherwise to the closest matching window depending on levels.
+
+    The seek position parameter is used internally to display away logs, if
+    omitted the whole file is shown.
+
+%9Examples:%9
+
+    /CAT -window /etc/network/interfaces
+    /CAT /home/mike/resume.txt
+    /CAT contact_details.txt
+
+%9See also:%9 CD, EXEC
 

docs/help/in/cd.in

@@ -1,8 +1,21 @@
 
+%9Syntax:%9
+
 @SYNTAX:cd@
 
-Changes the current working directory. Equivalent to UNIX
-'cd' command.
+%9Parameters:%9
 
-See also: DCC GET
+    The directory to change into.
+
+%9Description:%9
+
+    Changes the current active directory.
+
+%9Examples:%9
+
+    /CD /home/public_ftp
+    /CD /home/mike
+    /CD /var/log
+
+%9See also:%9 CAT
 

docs/help/in/channel.in

@@ -1,35 +1,48 @@
 
+%9Syntax:%9
+
 @SYNTAX:channel@
 
-Irssi can automatically join to specified channels in specified
-IRC networks. It can also automatically send the password when
-manually joining to channel without specifying the password.
+%9Parameters:%9
 
-/CHANNEL ADD [-auto | -noauto] [-bots <masks>] [-botcmd <command>]
-             <channel> <network> [<password>]
+    LIST:       Displays the list of configured channels.
+    ADD:        Adds a channel to your configuration.
+    MODIFY:     Modifies a channel in your configuration.
+    REMOVE:     Removes a channel from your configuration.
 
-With -bots and -botcmd arguments you can automatically send
-commands to someone in channel. This is useful for automatically
-getting ops for channels, for example
+    -auto:      Automatically join the channel.
+    -noauto:    Don't join the channel automatically.
+    -bots:      The list of hostnames send automated commands to.
+    -botcmd:    The automated commands to perform.
 
-/CHANNEL ADD -auto -bots "*!bot@bothost.org bot*!*@host2.org"
-             -botcmd "msg $0 op mypass" #channel ircnet
+    The channel and network to add to the configuration; you can optionally
+    specify the password of a channel.
 
-You can also use the -botcmd without -bots argument. The command is
-then sent whenever you join the channel.
+    If no parameters are given, the list of channels you have joined will be
+    displayed.
 
-If you want to remove some settings from existing channel record,
-for example bots, just give the -bots "" parameters to it. Password
-can be removed by setting it to - (or actually, "" works too).
+%9Description:%9
 
-You can remove the channels with
-/CHANNEL REMOVE <channel> <network>
+    Adds, removes or displays the configuration of channels; this method is
+    used to automate and simplify your workflow.
 
-/CHANNEL LIST displays list of channels with settings.
+    You can use the ADDALLCHANS command, which is a default alias, to add all
+    the channels you are present on into the configuration.
 
-/CHANNEL without any arguments displays list of channels you have
-joined. You can also use /CHANNEL to join to channels just as with
-/JOIN, like /CHANNEL #a.
+%9Examples:%9
 
-See also: TS, JOIN
+    /CHANNEL
+    /CHANNEL LIST
+    /CHANNEL ADD -auto #irssi liberachat
+    /CHANNEL ADD -auto #basementcat Quakenet secret_lair
+    /CHANNEL ADD -auto -bots '*!@*.irssi.org *!bot@irssi.org' -botcmd 'msg $0 op WzerTrzq' #hideout liberachat
+    /CHANNEL ADD -auto -bots 'Q!TheQBot@CServe.quakenet.org' -botcmd '^MSG Q op #irssi' #irssi Quakenet
+    /CHANNEL MODIFY -noauto #irssi liberachat
+    /CHANNEL REMOVE #hideout liberachat
+
+%9Special Example:%9
+
+    /ADDALLCHANS
+
+%9See also:%9 JOIN, TS
 

docs/help/in/clear.in

@@ -1,9 +1,19 @@
 
+%9Syntax:%9
+
 @SYNTAX:clear@
 
-This command clears the current window of all text. It is useful 
-for wiping a screen that has rendered improperly (such as due 
-to a bad termcap entry) or that contains sensitive information 
-(such as one's OPER password). 
+%9Parameters:%9
 
+    -all:    Clear all the windows
+
+    The window number to clear; if no argument is given, the active window
+    will be used.
+
+%9Description:%9
+
+    Scrolls up the text in the window and fills the window with blank lines; you
+    may want to use this to make new text start at the top of the window again.
+
+%9See also:%9 REDRAW, SCROLLBACK CLEAR
 

docs/help/in/completion.in

@@ -1,31 +1,35 @@
 
+%9Syntax:%9
+
 @SYNTAX:completion@
 
-Irssi can "complete" some words for you - you can write just first few letters
-of the word and press TAB (or any other key with action word_completion
-assigned). Then, irssi will choose the most probable matching word and inserts
-it to the command line. You can press TAB repetitively and irssi will replace
-the chosen word with another possible words matching to the letters you wrote.
+%9Parameters:%9
 
-The words chosen usually depend on their context - they can be filenames or
-command names, but most frequently they are nicks of people on same channels as
-you are. However, you can have global list of own completions, which apply to
-all contexts. This command is dedicated to maintaining of such a list.
+    -auto:      Inserts the completion without pressing a word completion
+                character.
+    -delete:    Removes the completion from the configuration.
 
-Without any parameters, /COMPLETION displays list of all user completions.
+    A key and the value to use as a replacement. If no argument is given, the
+    list of completions will be displayed.
 
-/COMPLETION [-auto] <prefix> <string> adds completion which gets triggered when
-you press TAB (or any other key with action word_completion assigned) after
-writing <prefix> specified and which expands to <string>. When -auto is
-specified, the completion gets triggered even when you press SPACE or ENTER (or
-any other key with action check_replaces assigned) after the <prefix>. If
-there's already some <prefix> completion in the list, it will get replaced.
+%9Description:%9
 
-/COMPLETION -delete <prefix> removes completion of <prefix> from the user
-completion list.
+    Replaces or completed words or letters; you can write just the first few
+    letters of the word and press TAB to insert a replacement.
 
-Note: When -auto is specified for the <prefix> you want to remove you have to 
-quote it like /COMPLETION -delete '<prefix>'. Works with doublequotes aswell.
+    When a replacement has been found, Irssi will choose the most probable
+    matching word and replaces it; you may press TAB repeatedly to swap between
+    matches.
 
-See also: BIND
+    If you want to remove a completion which has the auto parameter set, you
+    need to enclose the completion between "'" characters.
+
+%9Examples:%9
+
+    /COMPLETION w/h without
+    /COMPLETION -auto anywya anyway
+    /COMPLETION -delete 'anywya'
+    /COMPLETION -delete without
+
+%9See also:%9 BIND
 

docs/help/in/connect.in

@@ -1,21 +1,44 @@
 
+%9Syntax:%9
+
 @SYNTAX:connect@
 
-     -4, -6: specify explicitly whether to use IPv4 or IPv6 address
-     -ssl: use SSL when connecting
-     -ssl_cert: The SSL client certificate file (implies -ssl)
-     -ssl_pkey: The SSL client private key (if not included in the certificate file)
-     -ssl_verify: Verify servers SSL certificate
-     -ssl_cafile: File with list of CA certificates (implies -ssl_verify)
-     -ssl_capath: Directory with CA certificates (implies -ssl_verify)
-     -network: the network this connection belongs to
-     -ircnet: Same as -network. Deprecated. Do not use.
-     -host: the host
-     -!: don't autojoin channels
-     -rawlog: immediately open rawlog after connected
+%9Parameters:%9
 
-This command makes irssi to connect to specified server.
-Current connections are kept and a new one is created.
+    -4:                 Connects using IPv4.
+    -6:                 Connects using IPv6.
+    -tls:               Connects using TLS encryption.
+    -tls_cert:          The TLS client certificate file.
+    -tls_pkey:          The TLS client private key, if not included in the certificate file.
+    -tls_pass:          The password for the TLS client private key or certificate.
+    -tls_verify:        Verifies the TLS certificate of the server.
+    -tls_cafile:        The file with the list of CA certificates.
+    -tls_capath:        The directory which contains the CA certificates.
+    -tls_ciphers:       TLS cipher suite preference lists.
+    -tls_pinned_cert:   Pinned x509 certificate fingerprint.
+    -tls_pinned_pubkey: Pinned public key fingerprint.
+    -nocap:             Disable CAPREQ during connect
+    -noproxy:           Ignores the global proxy configuration.
+    -network:           The network this connection belongs to.
+    -host:              The hostname you would like to connect from.
+    -rawlog:            Immediately open rawlog after connecting.
+    -!:                 Doesn't autojoin channels.
+    -noautosendcmd:     Doesn't execute autosendcmd.
 
-See also: SERVER, DISCONNECT, RMRECONNS, SCONNECT
+    A network or server to connect to; you can optionally specify a custom port,
+    password and nickname.
+
+%9Description:%9
+
+    Opens a new connection to the specified network or server; existing
+    connections are kept.
+
+%9Examples:%9
+
+    /CONNECT liberachat
+    /CONNECT -6 liberachat
+    /CONNECT -4 -! -host staff.irssi.org -network liberachat irc.libera.chat
+    /CONNECT irc.irssi.org 6667 WzerT8zq mike
+
+%9See also:%9 DISCONNECT, RMRECONNS, SERVER
 

docs/help/in/ctcp.in

@@ -1,7 +1,23 @@
 
+%9Syntax:%9
+
 @SYNTAX:ctcp@
 
-Sends a CTCP message. For example CTCP ACTION, or CTCP VERSION.
+%9Parameters:%9
 
-See also: ME, ACTION
+    A target nickname or channel and a command.
+
+%9Description:%9
+
+    Sends a CTCP request towards the given target nickname or channel.
+
+%9Examples:%9
+
+    /CTCP mike PING
+    /CTCP #irssi VERSION
+    /CTCP bob USERINFO
+    /CTCP sarah CLIENTINFO
+    /CTCP john TIME
+
+%9See also:%9 ACTION, ME
 

docs/help/in/cycle.in

@@ -1,8 +1,22 @@
 
+%9Syntax:%9
+
 @SYNTAX:cycle@
 
-Cycles (leaves and joins) the current channel or the specified 
-channel.
+%9Parameters:%9
 
-See also: JOIN, PART
+    A channel and the message. If no argument is given, the active channel
+    will be used.
+
+%9Description:%9
+
+    Leaves and rejoins a channel.
+
+%9Examples:%9
+
+    /CYCLE
+    /CYCLE #irssi
+    /CYCLE #irssi BRB :)
+
+%9See also:%9 JOIN, PART
 

docs/help/in/dcc.in

@@ -1,37 +1,45 @@
 
+%9Syntax:%9
+
 @SYNTAX:dcc@
 
-/DCC LIST
-    - Shows all the open DCC connections.
-/DCC RESUME [<nick> [<file>]]
-    - Resumes a DCC SEND/GET connection.
-/DCC CHAT [-passive] [<nick>]
-    - Sends a chat connection request to remote client or accepts 
-      a chat connection if the remote end has already sent a request.
-      If -passive is used then the passive DCC protocol is used (as mIRC
-      can do). This is useful to bypass a NAT/firewall which limit your
-      possibility in listening for remote connections.
-/DCC GET [<nick> [<file>]]
-    - Gets the file offered by remote client. The file is downloaded and
-      saved into the directory specified by the `dcc_download_path' setting.
-/DCC SEND [-passive] [-append | -prepend | -flush | -rmtail | -rmhead]
-          <nick> <file> [<file> ...]
-    - Sends a DCC SEND request to remote client. Remote end has to accept
-      the request before the transmission can be started. Giving multiple
-      files queues them. File names may contain shell expansion
-      characters: * ? [] ~ (~ expansion may not be supported on all
-      platforms). Files with spaces in their names need to be quoted (eg.
-      "file name"). If -passive is used then the passive DCC protocol is
-      used (as mIRC and xchat > 2.0.7 can do). This is useful to bypass a
-      NAT/firewall which limit your possibility in  listening for remote
-      connections.
-/DCC SERVER [<+|-scf> <port>]
-    - Starts a DCC SERVER on the specified port. The remote can connect
-      to this server and initiate chat, send and fserve requests. You can
-      specify + or - using any combination of the flags 's' (Send),
-      'c' (Chat), or 'f' (Fserver).
-/DCC CLOSE <type> <nick> [<file>]
-    - Closes a DCC-connection. Type can be either SEND, GET or CHAT.
+%9Parameters:%9
 
-See also: CD
+    CHAT:        Initiates or accept a chat request.
+    GET:         Accepts a file transfer request.
+    RESUME:      Resumes a file transfer.
+    SERVER:      Starts a DCC server.
+    CLOSE:       Closes a DCC connection.
+    LIST:        Displays all the open DCC connections.
+
+    -passive:    Uses the passive DCC protocol.
+    -scf:        Use any combination of the flags to indicate:
+                     's' - send
+                     'c' - chat
+                     'f' - fserver
+
+    The nickname of the person to chat with, or the name of the file to
+    transfer.
+
+%9Description:%9
+
+    The DCC protocol is used to initiate client-to-client chat connections
+    and file transfers.
+
+    If you are behind NAT, or if the firewall is too restrictive, you might
+    want to try if using the passive parameter resolves your connection
+    problem.
+
+    You can send files which contain special character or spaces by enclosing
+    the filename within quotes. For example: 'my file with spaces.txt'.
+
+%9Examples:%9
+
+    /DCC CHAT mike
+    /DCC GET bob "summer vacation.mkv"
+    /DCC SEND sarah "summer vacation.mkv"
+    /DCC CLOSE get mike
+    /DCC CLOSE send bob "summer vacation.mkv"
+
+%9See also:%9 CD
 

docs/help/in/dehilight.in

@@ -1,7 +1,20 @@
 
+%9Syntax:%9
+
 @SYNTAX:dehilight@
 
-Removes the specified item from highlight list.
+%9Parameters:%9
 
-See also: HILIGHT
+    The id or mask of the highlight to remove.
+
+%9Description:%9
+
+    Removes the specified highlight from the configuration.
+
+%9Examples:%9
+
+    /DEHILIGHT 1
+    /DEHILIGHT 31
+
+%9See also:%9 HILIGHT
 

docs/help/in/deop.in

@@ -1,10 +1,23 @@
 
+%9Syntax:%9
+
 @SYNTAX:deop@
 
-Takes off the channel operator privileges from the
-specified nick(s). 
+%9Parameters:%9
 
-Wildcards in the nick are allowed.
+    A list of nicknames to deop.
 
-See also: OP
+%9Description:%9
+
+    Removes the channel operator privileges from the given nicknames; you may
+    use the wildcard character '*' in a nickname.
+
+%9Examples:%9
+
+    /DEOP mike
+    /DEOP bob sarah
+    /DEOP jo*n
+    /DEOP *
+
+%9See also:%9 DEVOICE, MODE, OP, VOICE
 

docs/help/in/devoice.in

@@ -1,10 +1,26 @@
 
+%9Syntax:%9
+
 @SYNTAX:devoice@
 
-Takes off the voice from the specified nick(s). This makes them
-not to be able to send messages to the moderated (+m) channel.
+%9Parameters:%9
 
-Wildcards in the nick are allowed.
+    A list of nicknames to devoice.
 
-See also: VOICE, MODE
+%9Description:%9
+
+    Removes the channel voice privileges from the given nicknames; you may use
+    the wildcard character '*' in a nickname.
+
+    If a channel is moderated, the users will require a voice or op in order to
+    be able to send messages to the channel.
+
+%9Examples:%9
+
+    /DEVOICE mike
+    /DEVOICE bob sarah
+    /DEVOICE jo*n
+    /DEVOICE *
+
+%9See also:%9 DEOP, MODE, OP, VOICE
 

docs/help/in/die.in

@@ -1,7 +1,15 @@
 
+%9Syntax:%9
+
 @SYNTAX:die@
 
-IRC operator command. Terminates the IRC server.
+%9Description:%9
 
-See also: OPER
+    Terminates the IRC server; this command is reserved for IRC operators.
+
+%9Examples:%9
+
+    /DIE
+
+%9See also:%9 KILL, OPER, WALLOPS
 

docs/help/in/disconnect.in

@@ -1,9 +1,26 @@
 
+%9Syntax:%9
+
 @SYNTAX:disconnect@
 
-Disconnects from the specified IRC-server.
-The server tags can be seen with:
-/SERVER
+%9Parameters:%9
 
-See also: CONNECT, SERVER
+    The network to disconnect from and the message to advertise; if no
+    parameters are given, the active server will be used.
+
+%9Description:%9
+
+    Disconnects from an IRC server; the list of all the servers you are
+    connected to can be retrieved via the SERVER command.
+
+    Use the wildcard character '*' if you want to disconnect from the active
+    server.
+
+%9Examples:%9
+
+    /DISCONNECT liberachat I'm off for today, take care!
+    /DISCONNECT * Vacation time :D
+    /DISCONNECT
+
+%9See also:%9 CONNECT, SERVER
 

docs/help/in/echo.in

@@ -1,5 +1,24 @@
 
+%9Syntax:%9
+
 @SYNTAX:echo@
 
-Prints text into the current window. Useful for scripts.
+%9Parameters:%9
+
+    -window:     Displays the output in the target window.
+    -level:      Displays the output with a given message level.
+
+    The text output; if no target is given, the active window will be used.
+
+%9Description:%9
+
+    Displays the given text.
+
+%9Examples:%9
+
+    /ECHO 1 + 1 = 2 :D
+    /ECHO Testing the ECHO command
+    /ECHO -window #irssi Special variables such as ${N} will not be expanded.
+
+%9See also:%9 CAT, EVAL, EXEC, LEVELS
 

docs/help/in/eval.in

@@ -1,6 +1,35 @@
 
+%9Syntax:%9
+
 @SYNTAX:eval@
 
-Evaluates the given commands and executes them. Internal variables
-are expanded. See the special_vars.txt file in the docs-directory.
+%9Parameters:%9
+
+    The commands to evaluate.
+
+%9Description:%9
+
+    Evaluates the given commands and executes them; you can use internal
+    variables and separate multiple commands by using the `;' character.
+    If the command contains a string with `$', `\' or `;' those characters
+    need to be escaped:
+
+        `$' -> `$$'
+        `\' -> `\\' (or even `\\\\', depending on where they are used)
+        `;' -> `\;'
+
+%9Examples:%9
+
+    /EVAL echo I am connected to ${S} on ${chatnet} as ${N}
+    /EVAL echo My user privileges are +${usermode}; echo Let's party!
+
+    to print `1;2$3\4':
+
+    /EVAL echo 1\;2$$3\\4
+
+%9References:%9
+
+    https://github.com/irssi/irssi/blob/master/docs/special_vars.txt
+
+%9See also:%9 CAT, CD, ECHO, EXEC
 

docs/help/in/exec.in

@@ -1,41 +1,50 @@
 
+%9Syntax:%9
+
 @SYNTAX:exec@
 
-     -: Don't print "process terminated ..." message
-     -nosh: Don't start command through /bin/sh
-     -out: Send output to active channel/query
-     -msg: Send output to specified nick/channel
-     -notice: Send output to specified nick/channel as notices
-     -name: Name the process so it could be accessed easier
+%9Parameters:%9
 
-     -window: Move the output of specified process to active window
-     -close: Forcibly close (or "forget") a process that doesn't die.
-             This only removes all information from irssi concerning the
-             process, it doesn't send SIGKILL or any other signal
-             to the process.
-     -<signal>: Send a signal to process. <signal> can be either numeric
-                or one of the few most common ones (hup, term, kill, ...)
+    -:               Suppresses the process termination notification.
+    -nosh:           Doesn't execute the command through /bin/sh.
+    -out:            Sends the output to the active channel or query.
+    -msg:            Sends the output to the specified nickname or channel.
+    -notice:         Sends the output to the specified nickname or channel as
+                     notices.
+    -name:           Gives the process the specified name.
+    -window:         Displays the output in the active window.
+    -close:          Forcibly closes a process that doesn't die.
+    -<signal>:       Sends the given signal to the process.
+    -in:             Sends text to the standard input of the process.
+    -interactive:    Executes the process in a new window item.
 
-     -in: Send text to standard input of the specified process
-     -interactive: Creates a query-like window item. Text written to it is
-                   sent to executed process, like /EXEC -in.
+    The command to execute; if no output parameter is given, the active window
+    will be used and if no parameters are given at all, the list of active
+    processes will be displayed.
 
-Execute specified command in background. Output of process is printed
-to active window by default, but can be also sent as messages or
-notices to specified nick or channel.
+%9Description:%9
 
-Processes can be accessed either by their ID or name if you named it.
-Process identifier must always begin with '%%' character, like %%0 or
-%%name.
+    Executes the specified command in the background; the process can be
+    accessed by its id or the name you gave it.
 
-Once the process is started, it's output can still be redirected
-elsewhere with the -window, -msg, etc. options. You can send text to
-standard input of the process with -in option.
+    The output of the process can be redirected to various targets, such as
+    a window, a channel, a nickname or a query.
 
--close option shouldn't probably be used if there's a better way to
-kill the process. It is meant to remove the processes that don't die
-even with SIGKILL. This option just closes the pipes used to
-communicate with the process and frees all memory it used.
+    The process identifier must always begin with the '%%' character. For
+    example %%0.
 
-EXEC without any arguments displays the list of started processes.
+    If you remove a process with the close parameter, it will only make Irssi
+    detach from it; the process will keep running until it terminates.
+
+%9Examples:%9
+
+    /EXEC
+    /EXEC ls
+    /EXEC -msg #irssi cat unicorn.txt
+    /EXEC -out cat /etc/passwd | grep $USER | awk -F: '{print $5}'
+    /EXEC -name ssh -nosh -interactive -window ssh staff.irssi.org
+    /EXEC -close mailserver
+    /EXEC -close %%0
+
+%9See also:%9 CAT, CD, ECHO, EVAL
 

docs/help/in/flushbuffer.in

@@ -1,6 +1,19 @@
 
+%9Syntax:%9
+
 @SYNTAX:flushbuffer@
 
-If either write_buffer_timeout or write_buffer_size have been set an immediate
-write of the buffers is forced.
+%9Description:%9
+
+    Forces an immediate flush of the buffers if the related settings are
+    enabled.
+
+%9Examples:%9
+
+    /FLUSHBUFFER
+
+    /SET write_buffer_size
+    /SET write_buffer_timeout
+
+%9See also:%9 REDRAW, SCROLLBACK
 

docs/help/in/format.in

@@ -1,9 +1,25 @@
 
+%9Syntax:%9
+
 @SYNTAX:format@
 
-   -reset
-   -delete
+%9Parameters:%9
 
-Allows you to view/change irssi's messages.
-Use this command with care.
+    -reset:     Restores the original value.
+    -delete:    Removes the format from the configuration.
+
+    The module name, the format name and the value; if no arguments are given,
+    the list of formats are displayed.
+
+%9Description:%9
+
+    Allows you to reconfigure the way messages are displayed.
+
+%9Examples:%9
+
+    /FORMAT irc away You have left planet earth
+    /FORMAT core not_good_idea I'm sorry sir, this broke my irony sensor; add -YES if you really mean it!
+    /FORMAT -reset irc away
+
+%9See also:%9 RELOAD, SAVE, SET
 

docs/help/in/hash.in

@@ -1,5 +1,22 @@
 
+%9Syntax:%9
+
 @SYNTAX:hash@
 
-Not available.
+%9Description:%9
+
+    This is an ancient command that is no longer used; if you on an IRC server
+    that supports this command, please contact us to we can update the
+    documentation.
+
+%9Examples:%9
+
+    /HASH
+
+%9References:%9
+
+    https://irssi.org
+    https://github.com/irssi
+
+%9See also:%9 DIE, KILL, OPER
 

docs/help/in/help.in

@@ -1,13 +1,27 @@
 
+%9Syntax:%9
+
 @SYNTAX:help@
 
-Shows help on commands. Try:
-  /HELP command
+%9Parameters:%9
 
-Also try, for example:
-  /SET beep
-or
-  /SET auto
+    The command to display the documentation for; if no argument is given, the
+    list of commands will be displayed.
 
-See also: 
+%9Description:%9
+
+    Displays the documentation for the given command.
+
+%9Examples:%9
+
+    /HELP
+    /HELP AWAY
+    /HELP CONNECT
+
+%9References:%9
+
+    https://irssi.org
+    https://github.com/irssi
+
+%9See also:%9 CONNECT, MSG, NETWORK, SERVER
 

docs/help/in/hilight.in

@@ -1,32 +1,43 @@
 
+%9Syntax:%9
+
 @SYNTAX:hilight@
 
-   -mask: Match only for nick, <text> is a nick mask
-   -regexp: <text> is a regular expression
-   -full: <text> must match to full words
-   -nick: Hilight only the nick, not the whole line (default)
-   -word: Hilight only the word (default with non-public messages)
-   -line: Hilight the whole line with the hilight color.
-   -color: Print the message with <color>. color is in %%code format
-           (see docs/formats.txt)
-   -actcolor: Color to show in statusbar activity, or don't change if %%n.
-   -level: Match only for <level> messages, default is
-           publics,msgs,notices,actions
-   -channels: Match only in <channels>
-   -priority: Priority to use when multiple hilights match. Default is 0.
+%9Parameters:%9
 
-Examples:
+    -nick:        Highlights only the nickname and not the whole line.
+    -word:        Highlights only the word and not the whole line.
+    -line:        Highlights the whole line.
+    -mask:        Highlights all messages from users matching the mask.
+    -full:        The text must match the full word.
+    -matchcase:   The text must match case.
+    -regexp:      The text is a regular expression.
+    -color:       The color to display the highlight in.
+    -actcolor:    The color to mark the highlight activity in the statusbar.
+    -level:       Matches only on the given message level.
+    -network:     Matches only on the given network.
+    -channels:    Matches only on the given channels.
+    -priority:    The priority to use when multiple highlights match.
 
-Hilight lines that have "mynick" word:
-  /HILIGHT mynick
+    The text to highlight on; if no argument is given, the list of highlights
+    will be displayed.
 
-Hilight all messages from "mynick":
-  /HILIGHT -mask mynick!*@*
+%9Description:%9
 
-Hilight lines that were written by nicks from *.fi with bold green
-  /HILIGHT -color %%G -mask *!*@*.fi
+    Highlights the keyword or pattern to make sure that you don't miss any
+    important messages.
 
-For regular expressions, see `man 7 regex`.
+%9Examples:%9
 
-See also: DEHILIGHT, SET HILIGHT
+    /HILIGHT
+    /HILIGHT mike
+    /HILIGHT -regexp mi+ke+
+    /HILIGHT -mask -color %%G bob!*@*.irssi.org
+    /HILIGHT -full -color %%G -actcolor %%Y redbull
+
+%9References:%9
+
+    https://github.com/irssi/irssi/blob/master/docs/formats.txt
+
+%9See also:%9 DEHILIGHT, LEVELS
 

docs/help/in/ignore.in

@@ -1,46 +1,55 @@
 
+%9Syntax:%9
+
 @SYNTAX:ignore@
 
-    -regexp: <pattern> is a regular expression
-    -full: <pattern> must match to full words
-    -pattern: <pattern> must match to the message's text
-    -except: *DON'T* ignore - overrides an existing ignore.
-    -replies: Ignore replies to nick in channels. For example
-              "/IGNORE -replies *!*@*.fi PUBLIC" ignores everyone
-              from Finland, but also anyone sending message
-              "tofinnishnick: blahblah".
-    -network: Ignore only on this network.
-    -ircnet: Same as -network. Deprecated. Do not use.
-    -channels: Ignore only in channels
-    -time: <secs> seconds after the ignore is removed
-    <mask>: Either a nick mask or list of channels
-    <levels>: List of levels to ignore. You can use -<level> to remove levels
-              from ignore.
-    <^levels>: List of levels to NOT ignore
-               (/ignore -except nick notices = /ignore nick ^notices)
+%9Parameters:%9
 
+    -regexp:      Indicates that the pattern is a regular expression.
+    -full:        Indicates that the pattern must match a full word.
+    -pattern:     The text pattern to ignore.
+    -except:      Negates the ignore.
+    -replies:     Also ignore nicknames who are talking to anyone who matches
+                  the ignore.
+    -network:     Ignores only on a specific network.
+    -channels:    Ignores only on specific channels.
+    -time:        The timeout to automatically remove the ignore.
+                  Accepts units specified in days, hours, minutes, seconds,
+                  milliseconds, or no unit for seconds.
 
-/IGNORE without any arguments displays list of ignores. If you want to remove
-some levels of the ignore, use /IGNORE <mask> -<level> -<level2> etc
+    The mask, channels and levels to ignore; if no argument is provided, the
+    list of ignores will be displayed.
 
-The best match always wins, so you can have:
+%9Description:%9
+
+    Ignores nicknames or text that matches a pattern.
+
+    The special level 'NO_ACT' can be used to ignore activity in the statusbar
+    without actually ignoring the message; this behavior is somewhat special
+    because it is allowed in addition to other ignores for the same target.
+    The special level 'HIDDEN' can be used to hide matching messages that can
+    later be revealed using /WINDOW HIDELEVEL -HIDDEN
+    The special level 'NOHILIGHT' can be used to suppress hilights without actually
+    ignoring the message.
+
+%9Examples:%9
+
+    /IGNORE
+    /IGNORE * JOINS
     /IGNORE * CTCPS
-    /IGNORE -except *!*@host.org CTCPS
-
-Examples:
-
-    /IGNORE * JOINS                         - ignore joins in all channels
-    /IGNORE #channel ALL -PUBLIC -ACTIONS   - ignore all but public/actions
-    /IGNORE #channel -JOINS                 - don't ignore joins anymore
-    /IGNORE -replies *!user@*.host.org ALL  - ignore user and all replies
-
-Some suggestions for ignoring annoying public aways:
-    /IGNORE -regexp -pattern "is (away|gone|back)" * ACTIONS
+    /IGNORE -except *!*@*.irssi.org CTCPS
+    /IGNORE #irssi ALL -PUBLIC -ACTIONS
+    /IGNORE -replies *!*@*.irssi.org ALL
+    /IGNORE -regexp -pattern (away|gone|back|playing|returned) * ACTIONS
+    /IGNORE -regexp -pattern (away|gone|back|playing|returned) #channel ACTIONS
     /IGNORE *zzz* NICKS
     /IGNORE *afk* NICKS
     /IGNORE *away* NICKS
+    /IGNORE #irssi NO_ACT JOINS PARTS QUITS
+    /IGNORE mike NO_ACT -MSGS
+    /IGNORE mike HIDDEN PUBLIC JOINS PARTS QUITS
+    /IGNORE -time 5days christmas PUBLICS
+    /IGNORE -time 300 mike PUBLICS
 
-For regular expressions, see `man 7 regex`.
-
-See also: UNIGNORE, SILENCE, ACCEPT
+%9See also:%9 ACCEPT, SILENCE, UNIGNORE
 

docs/help/in/info.in

@@ -1,6 +1,21 @@
 
+%9Syntax:%9
+
 @SYNTAX:info@
 
-Shows information about the IRC server software and the current
-server instance.
+%9Parameters:%9
+
+    The server to display the information for; if no argument is given, the
+    active server will be used.
+
+%9Description:%9
+
+    Displays information about the IRC server software.
+
+%9Examples:%9
+
+    /INFO
+    /INFO irc.libera.chat
+
+%9See also:%9 ADMIN
 

docs/help/in/invite.in

@@ -1,10 +1,21 @@
- 
+
+%9Syntax:%9
+
 @SYNTAX:invite@
 
-Invites the specified nick to the current or specified channel.
+%9Parameters:%9
 
-Example:
-   /INVITE buddy #mychannel
+    The nickname to invite and the channel to invite him or her to; if no
+    channel is given, the active channel will be used.
 
-See also: MODE
+%9Description:%9
+
+    Invites the specified nick to a channel.
+
+%9Examples:%9
+
+    /INVITE mike
+    /INVITE bob #irssi
+
+%9See also:%9 MODE, WHOIS
 

docs/help/in/invitelist.in

@@ -1,9 +0,0 @@
-
-@SYNTAX:invitelist@
-
-Shows the +I modes of the current channel. +I mode
-allows free joins of clients with certain userhost masks
-even if the channel is invite only.
-
-See also: INVITE, MODE
-

docs/help/in/ircnet.in

@@ -1,4 +0,0 @@
-IRCNET
-
-Deprecated. Use NETWORK instead.
-

docs/help/in/irssiproxy.in

@@ -0,0 +1,14 @@
+
+@SYNTAX:irssiproxy@
+
+%9Description:%9
+
+    Displays the list of clients connected to irssiproxy.
+
+%9Examples:%9
+
+    /IRSSIPROXY
+    /IRSSIPROXY STATUS
+
+%9See also:%9 LOAD PROXY, SET irssiproxy
+

docs/help/in/ison.in

@@ -1,7 +1,20 @@
 
+%9Syntax:%9
+
 @SYNTAX:ison@
 
-Tells whether specified nicks (space-separated) are online.
+%9Parameters:%9
 
-See also: WHOIS, WHOWAS, NOTIFY
+    The nicknames, separated by space, to check.
+
+%9Description:%9
+
+    Displays whether the specified nicknames are online.
+
+%9Examples:%9
+
+    /ISON mike
+    /ISON sarah bob
+
+%9See also:%9 NOTIFY, WHOWAS, WHOIS
 

docs/help/in/join.in

@@ -1,11 +1,26 @@
 
+%9Syntax:%9
+
 @SYNTAX:join@
 
-Joins a specified channel. Channel names usually begin with #-sign,
-which may be omitted here.
+%9Parameters:%9
 
-JOIN is aliased to J by default. Example: /j irssi
-(This joins to the channel #irssi)
+    -window          Joins a channel in the active window.
+    -invite          Joins the channel you were last invited to.
+    -<server tag>    The server tag on which you want to join the channel.
 
-See also: PART, WINDOW CLOSE
+    The channel names, separated by a comma, to join and the channel key.
+
+%9Description:%9
+
+    Joins the given channels.
+
+%9Examples:%9
+
+    /JOIN #irssi
+    /JOIN #basementcat secret_lair
+    /JOIN -invite
+    /JOIN -liberachat #github,#libera,#irssi
+
+%9See also:%9 KICK, PART
 

docs/help/in/kick.in

@@ -1,16 +1,24 @@
 
+%9Syntax:%9
+
 @SYNTAX:kick@
 
-This command "kicks" the specified user off of the specified 
-channel. It is typically used to remove troublemakers, flooders, 
-or people otherwise making a nuisance of themselves on the channel. 
-The reason for the kick is recommended, but not required by the IRC 
-servers.
+%9Parameters:%9
 
-If the <channel> is omitted, removes the nick from the current
-channel.
+    The channel and the nicknames, separated by a comma, to kick from the
+    channel and the reason thereof; if no channel is given, the active channel
+    will be used.
 
-The default alias for /KICK is /K.
+%9Description:%9
 
-See also: KNOCKOUT
+    Removes the given nicknames from the specified channel; this command is
+    typically used to remove troublemakers, flooders or people otherwise making
+    a nuisance of themselves.
+
+%9Examples:%9
+
+    /KICK mike Please... chill down!
+    /KICK #irssi bob,sarah Stop flooding!
+
+%9See also:%9 BAN, KICKBAN, KNOCKOUT
 

docs/help/in/kickban.in

@@ -1,10 +1,22 @@
 
+%9Syntax:%9
+
 @SYNTAX:kickban@
 
-Kicks off and bans a nick from the current channel.
-A reason for the kick can be supplied.
+%9Parameters:%9
 
-Default alias for /KICKBAN is /KB.
+    The channel and the nicknames, separated by a comma, to kick and ban from
+    the channel and the reason thereof; if no channel is given, the active
+    channel will be used.
 
-See also: KNOCKOUT, BANTYPE
+%9Description:%9
+
+    Removes and then bans the given nicknames from the specified channel.
+
+%9Examples:%9
+
+    /KICKBAN mike Please... chill down!
+    /KICKBAN #irssi bob,sarah You guys broke the rules for the last time.
+
+%9See also:%9 BAN, KICK, KNOCKOUT
 

docs/help/in/kill.in

@@ -1,18 +1,24 @@
 
+%9Syntax:%9
+
 @SYNTAX:kill@
 
-IRC operator command.
+%9Parameters:%9
 
-KILL is used to forcibly remote a client from the irc network. 
-It works similarly to KICK, except that a reason must be 
-given (even if it is meaningless or flat-out wrong). 
+    The nickname to remove from the network and the reason thereof.
 
-In general, KILL is useful only as a warning tool for abusive 
-users. Modern irc clients (this one included) have automated 
-means for reconnecting to a server after a disconnection (whether 
-due to a KILL or something else), so KILL is by no means a 
-permanent solution. It is not intended as a means for personal 
-vendettas; this practice is generally frowned upon. 
+%9Description:%9
 
-See also: OPER
+    Terminates a nickname's connection from the network; this command is
+    reserved for IRC operators.
+
+    You should not use this command for personal vendettas or for trolling;
+    these practices are generally frowned upon.
+
+%9Examples:%9
+
+    /KILL mike Get off my lawn
+    /KILL bob Stop breaking the network rules!
+
+%9See also:%9 DIE, OPER, WALLOPS
 

docs/help/in/knock.in

@@ -1,16 +1,30 @@
 
+%9Syntax:%9
+
 @SYNTAX:knock@
 
-Works only in some IRC networks (hybrid-like ircds).
+%9Parameters:%9
 
-KNOCK is a feature that lets you request access to a channel they cannot join without an invite, a key or a raised limit.
+    The channel you wish to get invited to.
 
-The following conditions must be met for KNOCK to work:
+%9Description:%9
 
- - You are not banned from the channel
- - Channel is not private (+p)
- - You are not already on the channel
- - Channel is invite only (+i), has a key (+k) or limit is full
+    Sends an invitation request to the channel operators of the target channel;
+    this command may not work on all IRC servers.
 
-When successful KNOCK is issued, it sends a notice to channel operators. Use of KNOCK is rate limited by the server.
+    The following conditions must be met:
+
+        * You are not banned from the channel.
+        * The channel is not private.
+        * You may not be already in the channel.
+        * The channel must be invite only, have a key or has exceeded its user
+          limit.
+
+%9Examples:%9
+
+    /KNOCK #irssi
+    /KNOCK #libera
+    /KNOCK #github
+
+%9See also:%9 INVITE, JOIN
 

docs/help/in/knockout.in

@@ -1,11 +1,26 @@
 
+%9Syntax:%9
+
 @SYNTAX:knockout@
 
-Kicks user off the channel and bans him/her. Ban
-lasts the given number of seconds or 5 minutes
-by default.
+%9Parameters:%9
 
-Default alias for /KNOCKOUT is /KN.
+    The time, expressed in seconds, the nicknames, separated by a comma, and the
+    reason thereof; if no time is provided, the ban will be lifted after 5
+    minutes.
 
-See also: BAN, KICK
+%9Description:%9
+
+    Removes and then bans the given nicknames from the active channel; the ban
+    will be automatically lifted after the specified time.
+
+    The ban will not be lifted if you leave the channel or disconnect from the
+    network.
+
+%9Examples:%9
+
+    /KNOCKOUT 3600 mike Your connection is unstable.
+    /KNOCKOUT bob,sarah Chill down a bit.
+
+%9See also:%9 BAN, KICK, KICKBAN
 

docs/help/in/lastlog.in

@@ -1,22 +1,43 @@
 
+%9Syntax:%9
+
 @SYNTAX:lastlog@
 
-    -clear: remove all lastlog lines from window
+%9Parameters:%9
 
-    -: don't print the "Lastlog:" and "End of Lastlog" messages.
-    -file: write lastlog to file instead of screen
-    -window: which window's lastlog to check (output is always to active)
-    -case: Case-sensitive matching
-    -force: Force displaying lastlog even if it's longer than 1000 lines
-    -new: show only lines since last /LASTLOG
-    -regexp: `text' is a regular expression
-    -word: `text' must match to full words
-    -<level>: levels to check (default is all; /help levels for details)
-    <pattern>: text to search for, or all if empty
-    <count>: maximum number of lines to show
-    <start>: skip the last `start' lines
+    -:          Doesn't print the 'Lastlog:' and 'End of Lastlog' messages.
+    -file:      Output the lastlog to a file instead of the active window.
+    -window:    Specifies the window to check.
+    -new:       Only displays results since the previous lastlog.
+    -away:      Only displays results since you previous away status.
+    -<level>:   Specifies the levels to check (e.g. -joins -quits -hilight)
+    -clear:     Removes the previous results from the active window.
+    -count:     Displays how many lines match.
+    -case:      Performs a case-sensitive matching.
+    -date:      Prepends each row with the message's date
+    -regexp:    The given text pattern is a regular expression.
+    -word:      The text must match full words.
+    -force:     Forces to display the lastlog, even if it exceeds 1000 lines.
+    -after:     Include this many lines of content after the match.
+    -before:    Include this many lines of content before the match.
+    -<#>:       Include this many lines of content around the match.
+    <count>:    Display a maximum number of `count' lines.
+    <start>:    Skip the last `start' lines.
 
-Shows the given number of lines of log from the current window.
+    The pattern to search for and the maximum of lines to display; if no
+    parameter is given, the entire window buffer will be displayed.
 
-See also:
+%9Description:%9
+
+    Searches the active window for a pattern and displays the result.
+
+%9Examples:%9
+
+    /LASTLOG holiday
+    /LASTLOG 'is on vacation' 10
+    /LASTLOG -force -file ~/mike.log 'mike'
+    /LASTLOG -hilight
+    /LASTLOG -5 searchterm
+
+%9See also:%9 HILIGHT, SCROLLBACK
 

docs/help/in/layout.in

@@ -1,13 +1,28 @@
 
+%9Syntax:%9
+
 @SYNTAX:layout@
 
-Saves the current window layout to configuration (yes, you'll still
-need to use /SAVE to save the configuration to file). Next time you run
-irssi, all the channels and queries are exactly in the same windows
-where they were when you called /LAYOUT SAVE.
+%9Parameters:%9
 
-Channels aren't actually joined in those windows immediately, they're
-just marked "next time you join to '#channel' in server that has tag
-'ircnet' place it to this window".
+    SAVE:     Saves your layout to the configuration.
+    RESET:    Removes the saved layout from the configuration.
+
+%9Description:%9
+
+    Saves the layout of your window configuration; the next time you connect
+    to the server, you will join the channels in the same window as before.
+
+    This method enables you to keep the same window layout when you start Irssi
+    the next time.
+
+    You will need to use the SAVE command to confirm and commit the changes
+    into the configuration file.
+
+%9Examples:%9
+
+    /LAYOUT SAVE
+    /LAYOUT RESET
+
+%9See also:%9 SAVE, WINDOW
 
-/LAYOUT RESET removes the saved layout.

docs/help/in/levels.in

@@ -1,35 +1,43 @@
-Message levels (or in short, levels) are used almost everywhere.
-They describe what kind of messages we're dealing with. Here's a
-list of them all:
 
-    CRAP            - Can be almost anything
-    MSGS            - Private messages
-    PUBLIC          - Public messages in channel
-    NOTICES         - Notices
-    SNOTES          - Server notices
-    CTCPS           - CTCP messages
-    ACTIONS         - Actions (/me) - usually ORed with PUBLIC or MSGS
-    JOINS           - Someone joins a channel
-    PARTS           - Someone parts a channel
-    QUITS           - Someone quits IRC
-    KICKS           - Someone gets kicked from channel
-    MODES           - Channel mode is changed
-    TOPICS          - Channel topic is changed
-    WALLOPS         - Wallop is received
-    INVITES         - Invite is received
-    NICKS           - Someone changes nick
-    DCC             - DCC related messages
-    DCCMSGS         - DCC chat messages
-    CLIENTNOTICE    - Irssi's notices
-    CLIENTERROR     - Irssi's error messages
-    CLIENTCRAP      - Some other messages from Irssi
+%9Description:%9
 
-And a few special ones that could be included with the
-levels above:
+    These are the message levels that are used throughout Irssi; they describe
+    what kind of message is displayed.
 
-    HILIGHT         - Text is highlighted
-    NOHILIGHT       - Don't check highlighting for this message
-    NO_ACT          - Don't trigger channel activity when printing
-                      this message
-    NEVER           - Never ignore or log this message
+    These are the common levels you can use:
+
+        ACTIONS         Actions by a nickname.
+        CLIENTCRAP      Irssi's internal messages.
+        CLIENTERROR     Irssi's internal error messages.
+        CLIENTNOTICE    Irssi's internal notices.
+        CRAP            Can be almost anything.
+        CTCPS           CTCP messages.
+        DCC             DCC protocol related messages.
+        DCCMSGS         DCC chat messages.
+        INVITES         An invite is received.
+        JOINS           A nickname joins a channel.
+        KICKS           A nickname gets kicked from a channel.
+        MODES           A channel mode is modified.
+        MSGS            Private messages.
+        NICKS           A nickname changes to another nickname.
+        NOTICES         Private notices.
+        PARTS           A nickname leaves a channel.
+        PUBLIC          Public messages in a channel.
+        PUBNOTICES      Public notices in a channel.
+        QUITS           A nickname disconnects from IRC.
+        SNOTES          Notices sent from a server.
+        TOPICS          A channel topic is modified.
+        WALLOPS         A wallop is received.
+
+    These are the special levels you can use:
+
+        HILIGHT         The text is highlighted.
+        NEVER           Never ignores or logs the message.
+        HIDDEN          Hides the message when window HIDELEVEL includes HIDDEN.
+        NO_ACT          Doesn't trigger any activity in the statusbar.
+        NOHILIGHT       The text is not highlighted.
+                        Suppresses hilights when used with /ignore.
+
+    When using levels from Irssi scripts, you need to prepend the level with
+    'MSGLEVEL_'; for example 'CRAP' becomes 'MSGLEVEL_CRAP'.
 

docs/help/in/links.in

@@ -1,9 +1,22 @@
 
+%9Syntax:%9
+
 @SYNTAX:links@
 
-Shows the links between the IRC servers of the
-current IRC network. If a wildcard parameter is
-specified, shows only the matching entries.
+%9Parameters:%9
 
-See also: MAP
+    The server to search on and the string to match on; if no arguments are
+    given, the list of links of the active server will be displayed.
+
+%9Description:%9
+
+    Displays the links between an IRC server and its connections.
+
+%9Examples:%9
+
+    /LINKS
+    /LINKS ircsource.irssi.org
+    /LINKS ircsource.irssi.org *.hub
+
+%9See also:%9 LUSERS, MAP
 

docs/help/in/list.in

@@ -1,16 +1,38 @@
 
+%9Syntax:%9
+
 @SYNTAX:list@
 
-Lists the channel names. Trying to list all the channel 
-names usually causes you to be disconnected from the 
-server with the reason "Excess flood", as usually all
-40000 channels form together and server naively attempts
-to send you them.
+%9Parameters:%9
 
-Thus, on IRCNet, you should rather use service ALIS
-(Advanced Listing Service), which will allow you to query
-for channel with specific name, topic, mode or usercount.
-Type /SQUERY ALIS HELP to get more info about it.
+    -yes:    Confirms that you want to receive a large amount of data.
 
-See also: SQUERY
+    If the exact name of a channel is given, the only information about this
+    channel is requested; otherwise, a list of all channels will be displayed.
+
+%9Description:%9
+
+    Displays the channel names that match your request; requesting all channels
+    may cause the server to disconnect you for flooding.
+
+%9Examples:%9
+
+    /LIST
+    /LIST -yes
+    /LIST #ubuntu
+    /LIST #*ubuntu*,>1
+
+%9Remarks:%9
+
+    Not all networks support server-side filtering. Some provide a network
+    service or service bot instead; on IRCnet, you may use the List service:
+
+    /SQUERY Alis HELP
+
+    Other networks with service bots (like ChanServ) may also provide a list
+    service bot (confirm with /WHOIS ALIS):
+
+    /MSG Alis HELP
+
+%9See also:%9 STATS, SQUERY, WHOIS
 

docs/help/in/load.in

@@ -1,16 +1,23 @@
 
+%9Syntax:%9
+
 @SYNTAX:load@
 
-Load a plugin. If full path isn't given, irssi searches the plugin from
-directories:
+%9Parameters:%9
 
- ~/.irssi/modules/
- <install dir, /usr/local or /usr maybe>/lib/irssi/modules/
+    The name of the module and submodule to load.
 
-See plugins page of http://www.irssi.org/ to see if there's any plugins
-you'd want to use.
+%9Description:%9
 
-To load a perl script you should use /SCRIPT.
+    Loads a plugin; if the full path isn't given, it will attempt to load from
+    common directories in your installation path.
 
-See also: UNLOAD
+    To load a perl script, you must use the SCRIPT command.
+
+%9Examples:%9
+
+    /LOAD fish
+    /LOAD ~/irssi-fish/libfish.so
+
+%9See also:%9 SCRIPT, UNLOAD
 

docs/help/in/log.in

@@ -1,41 +1,48 @@
 
+%9Syntax:%9
+
 @SYNTAX:log@
 
-     -noopen: Create the entry to log list, but don't start logging
-     -autoopen: Automatically open this log file at startup
-     -<server tag>: Targets are logged only in this server
-     -targets: Log only in specified channels/nicks (space separated list)
-     -window: Log output in the window. Active window is used by default, or
-              you can give the window's refnum in -targets.
-     <filename>: File name where to log, it is parsed with
-                 strftime(), so %%d=day, etc. see "man strftime" for
-                 more info.
-     <levels>: Defaults to ALL
-     <id>: ID number of log.   
+%9Parameters:%9
 
-/SET log_create_mode <mode> - Specifies what file mode to use with
-     the created log files. Default is 0644.
+    OPEN:             Opens a log file.
+    CLOSE:            Closes a log file.
+    START:            Starts logging a log entry.
+    STOP:             Stops logging a log entry.
 
-All of these are parsed with strftime():
-/SET log_timestamp <text> - Specifies the time stamp format.
-     Default is "%%H:%%M ".
-/SET log_open_string <text> - Text written to log when it's opened
-/SET log_close_string <text> - Text written to log when it's closed
-/SET log_day_changed <text> - Text written to log when day changes
+    -noopen:          Saves the entry in the configuration, but doesn't actually
+                      start logging.
+    -autoopen:        Automatically opens the log at startup.
+    -window:          Displays the output to the active window, or the window
+                      specified in the targets parameter.
+    -<server tag>:    The server tag the targets must be on.
+    -targets:         Logs the specified nicknames or channels.
+    -colors:          Also log the color codes of the messages.
 
-NOTE: Log files are locked after opened, so two Irssis can't
-accidentally try to write to the same log file.
+    The filename of the log and the levels to match; if no argument is given,
+    the list of open logs will be displayed.
 
-Examples:
-        
-/LOG OPEN -targets cras ~/irclogs/cras.log MSGS
-     - Logs all messages from/to nick `cras'
+%9Description:%9
 
-/LOG OPEN -targets #linux ~/irclogs/linux/linux-%%Y-%%m-%%d
-     - Logs all messages in channel #linux. Log is rotated daily, so
-       logs in 1. May 2000 goes to file "linux-2000-05-01", when the
-       day is changed, Irssi closes the log and starts logging to
-       "linux-2000-05-02" etc.
+    Opens a log file and stores the messages of the given targets into it; the
+    log files will be locked so multiple clients cannot log to the same file.
 
-See also: SET LOG, WINDOW LOG
+    You may use any of the date formats to create a log rotation; we strongly
+    recommend you to enable autolog if you are interested in keeping logs.
+
+%9Examples:%9
+
+    /LOG OPEN -targets mike ~/irclogs/mike.log MSGS
+    /LOG OPEN -targets #irssi ~/irclogs/liberachat/irssi-%%Y-%%m-%%d
+    /LOG CLOSE ~/irclogs/liberachat/irssi-%%Y-%%m-%%d
+    /LOG STOP ~/irclogs/liberachat/irssi-%%Y-%%m-%%d
+    /LOG START ~/irclogs/liberachat/irssi-%%Y-%%m-%%d
+
+    /SET autolog ON
+
+%9References:%9
+
+    https://github.com/irssi/irssi/blob/master/docs/formats.txt
+
+%9See also:%9 SET LOG, WINDOW LOG
 

docs/help/in/lusers.in

@@ -1,5 +1,24 @@
 
+%9Syntax:%9
+
 @SYNTAX:lusers@
 
-Shows user statistics of the current IRC network.
+%9Parameters:%9
+
+    The server to search on and the remote server to search on; if no arguments
+    are given, the active server will be used.
+
+%9Description:%9
+
+    Displays the user statistics of the active or remote server.
+
+    The parameters to search on a remote server are no longer supported on most
+    IRC servers; we no longer provide examples for remote LUSERS to avoid all
+    confusion.
+
+%9Examples:%9
+
+    /LUSERS
+
+%9See also:%9 LINKS, MAP
 

docs/help/in/map.in

@@ -1,7 +1,16 @@
 
+%9Syntax:%9
+
 @SYNTAX:map@
 
-Works only in some IRC networks and is often restricted to IRC operators.
+%9Description:%9
 
-Shows a graphical map of the IRC network, often with user counts.
+    Displays the network map of an IRC network; this command is usually
+    reserved for IRC operators and does not work on all servers.
+
+%9Examples:%9
+
+    /MAP
+
+%9See also:%9 DIE, LINKS, LUSERS
 

docs/help/in/me.in

@@ -1,8 +1,21 @@
 
+%9Syntax:%9
+
 @SYNTAX:me@
 
-Sends a CTCP ACTION to the current channel or query.
-For example: /me sits back.
+%9Parameters:%9
 
-See also: ACTION, CTCP
+    The message to emote.
+
+%9Description:%9
+
+    Sends an action emote to the active nickname or channel.
+
+%9Examples:%9
+
+    /ME is hungry!
+    /ME had an awesome day @ work
+    /ME is happy it's Friday
+
+%9See also:%9 ACTION, CTCP
 

docs/help/in/meson.build

@@ -0,0 +1 @@
+# don't forget to add new help files to ../meson.build

docs/help/in/mircdcc.in

@@ -1,11 +1,28 @@
 
+%9Syntax:%9
+
 @SYNTAX:mircdcc@
 
-Selects whether to send mIRC style CTCPs in DCC chat
-session.
+%9Parameters:%9
 
-If a mIRC user sends first a CTCP, mIRC style CTCPs is
-automatically selected for that DCC Chat session.
+    ON:     Enables mIRC compatibility mode.
+    OFF:    Disables mIRC compatibility mode.
 
-See also: SET MIRC
+%9Description:%9
+
+    After establishing a DCC CHAT connection that you initiated, you might
+    encounter some protocol issues if the target is using mIRC.
+
+    If you or your target sees some unexpected output or behavior inside a DCC
+    CHAT session, use this command to enable mIRC compatibility mode.
+
+    When receiving a connection from an mIRC user, the compatibility mode will
+    automatically be enabled.
+
+%9Examples:%9
+
+    /MIRCDCC ON
+    /MIRCDCC OFF
+
+%9See also:%9 ACTION, CTCP, DCC
 

docs/help/in/mode.in

@@ -1,82 +1,77 @@
 
+%9Syntax:%9
+
 @SYNTAX:mode@
 
-Common channel modes are:
+%9Parameters:%9
 
-     i - Invite only - People can't join to channel without being
-         /INVITEd, or being in invite list (+I, see below).
-     m - Moderated - People who don't have voices (+v) can't send
-         messages to channel
-     p - Private - People who aren't joined to channel can't see it
-         for example with /WHOISing people who are in channel.
-     s - Secret - Like private, but the channel isn't displayed in
-         /LIST's output.
-     n - No external msgs - Without this mode, anyone can send messages
-         to channel without even being joined.
-     t - Topic can be changed only by channel operators.
+    The target nickname or channel and the modes with their parameters to set or
+    remove.
 
-     k <key> - Channel password (aka. key) - The channel can't be joined
-               without specifying the channel key (see section 6.2).
+    If the target nickname or channel is omitted, the active nickname or channel
+    will be used.
 
-     l <count> - User limit - No more than <count> people can join to
-                 channel. This can be overridden with /INVITE with some
-                 servers.
+%9Description:%9
 
-                 This is usually used for protecting channel from join
-                 flooding, like some bot allows max. 5 users to join in
-                 one minute or so.
+    Modifies the user or channel modes for which you are privileged to modify.
 
-     b - Set/remove ban. For example MODE #channel +b *!*@*.org bans
-         everyone from .org domain.
+    You can specify multiple modes in one command and prepend them by using the
+    '+' sign to set or '-' sign to unset; modes that require a parameter will be
+    retrieved from the argument list.
 
-         If someone from .org domain was already in channel before the
-         ban was set, he/she cannot send any messages to channel (doesn't
-         work with all servers).
+    Some common channel modes are:
 
-         Bans can also be overridden with /INVITE, although many stupid
-         IRC clients automatically kick the user out because they see
-         the ban and think that because of it the user shouldn't be in
-         the channel (doesn't work with all servers).
+        b <mask>:        Adds or removes a ban; a ban will prevent a user who
+                         matches the given mask from joining the channel unless
+                         he or she is invited or in the exempt list.
+        e <mask>:        Adds or removes a ban exception; users who match a mask
+                         on the exempt list are able to join a channel even if
+                         they also match an entry on the ban list.
+        i:               When enabled, users need to be invited into the channel
+                         or have a matching entry in the invite list.
+        I <mask>:        Adds or removes an invite; users who match a mask on
+                         the invite list are able to join even if the channel is
+                         set to invite only.
+        k <key>:         Adds or removes a channel key, aka a password; users
+                         will not be able to join the channel without providing
+                         the key.
+        l <count>:       Adds, removes or updates the maximum amount of users
+                         that may join the channel.
+        m:               When enabled, users who are not opped or voiced cannot
+                         send messages to the channel.
+        n:               When enabled, users who are not on the channel cannot
+                         send messages to it.
+        p:               When enabled, the channel will not be displayed in your
+                         WHOIS output.
+        s:               When enabled, the channel will not be displayed in the
+                         LIST output.
+        t:               When enabled, users who are not opped or voices cannot
+                         modify the channel topic.
+        o <nickname>:    Adds or removes the operator status from a nickname.
+        v <nickname>:    Adds or removes the voice status from a nickname.
 
-     e - Ban exceptions. You could for example ban everyone from
-         *!*@*.org but set ban exception to *!*@*.host.org - does not work
-         with all servers.
+    Some common user modes are:
 
-     I - Invite list. If channel is invite only (+i), people in this
-         list can join it without being /INVITEd - does not work with all
-         servers.
+        i:               When enabled, other users will not be able to see you
+                         on a WHO output unless they are in the channel
+                         themselves.
+        w:               When enabled, you will receive WALLOP messages from IRC
+                         operators.
+        s:               When enabled, you will receive special notices or debug
+                         messages from the server.
 
-         This is excellent for in-country channels that don't want
-         foreigners (spammers!) to join the channel, for example setting
-         channel's mode to +i and +I *!*@*.fi allows only finnish people
-         to join the channel. In addition to this, there's usually a bot
-         in the channels and sending /MSG bot invite command to it
-         /INVITEs you to the channel.
+    Many networks have additional user and channel modes; we highly recommend
+    you to read the documentation of the networks you frequently connect to and
+    maximize your IRC experience.
 
-         On IRCnet, the ':' feature in channel names can also be used for
-         a similar effect, see section 6.2.
+%9Examples:%9
 
-     o <nick> - Grant or revoke channel operator status from nick
-     v <nick> - Grant or revoke voice status from nick, only people with
-                +v (or +o) can talk to channel when it's moderated (+m).
+    /MODE #irssi +o mike
+    /MODE #irssi -o+iI mike mike!*@*.irssi.org
+    /MODE +b mike!*@*.irssi.org
+    /MODE -o mike
+    /MODE +impsnkl secret_hideout 100
+    /MODE mike +iw
 
-You can send multiple mode changes with one mode command:
-
-/MODE #channel +nto-o+v nick1 nick2 nick3
-
-This would set channel's mode to +nt, give ops to nick1, take ops
-from nick2 and give voices to nick3.
-
-You can set only a limited number of modes that require an argument
-in one command. In IRCnet it's 3, in EFnet it's 4 and in many others
-it's 6. If it's not known, Irssi defaults to 3. Irssi will also
-automatically split them, so you can use /MODE +oooooo n1 n2 ...
-command to op 6 people and Irssi will split it to two commands in
-IRCnet/EFnet.
-
-Many networks have additional modes and/or change the meaning of existing
-modes. Check the documentation for the network or the server software in
-use for details.
-
-See also: OP, DEOP, VOICE, DEVOICE, BAN, UNBAN
+%9See also:%9 BAN, DEOP, DEVOICE, OP, UNBAN, VOICE
 

docs/help/in/motd.in

@@ -1,7 +1,22 @@
 
+%9Syntax:%9
+
 @SYNTAX:motd@
 
-Shows the motd of the current or specified server. This contains
-usually some useful info on the server, administrator and
-the rules.
+%9Parameters:%9
+
+    The server or the server the target nickname is on; if no parameter is
+    given, the active server will be used.
+
+%9Description:%9
+
+    Displays the welcome message of an IRC server.
+
+%9Examples:%9
+
+    /MOTD
+    /MOTD irc.libera.chat
+    /MOTD bob
+
+%9See also:%9 ADMIN, INFO, LINKS, MAP
 

docs/help/in/msg.in

@@ -1,15 +1,33 @@
 
+%9Syntax:%9
+
 @SYNTAX:msg@
 
-Sends a message to a nick or a channel. Usually this
-is used for sending private messages to other persons.
+%9Parameters:%9
 
-Examples:
+    -<server tag>:    The server tag the targets are on.
+    -channel:         Indicates that the target is a channel.
+    -nick:            Indicates that the target is a nickname.
 
-/MSG friend Hi, what's up?
+    The target nickname or channel and the message to send.
 
-/MSG #irssi Hello, is the new gtk-version out already?
-(This format is rarely needed.)
+    The target can be a comma delimited list of targets, ie
+    nick1,nick2 or #chan1,#chan2
 
-See also: CTCP
+    Or one of the following special targets:
+      * : Use the active nickname or channel
+      , : Last person who sent you a /msg
+      . : Last person you sent a /msg to
+
+%9Description:%9
+
+    Sends a message to a nickname or channel.
+
+%9Examples:%9
+
+    /MSG mike Hi, what's up?
+    /MSG #irssi I am awesome :)
+    /MSG * Do you want to build a snowman?
+
+%9See also:%9 ACTION, DCC, JOIN
 

docs/help/in/names.in

@@ -1,21 +1,27 @@
 
+%9Syntax:%9
+
 @SYNTAX:names@
 
-     -ops: show channel operators in list
-     -halfops: show half operators in list
-     -voices: show voiced people in list
-     -normal: show rest of the people in list
+%9Parameters:%9
 
-Shows the names (nicks) in the specified channels. /NAMES ** shows all
-nicks in all channels, you probably don't want to do this.
+    -count:      Displays the amount of users in the channel.
+    -ops:        Displays the channel operators.
+    -halfops:    Displays the channel demi-operators.
+    -voices:     Displays the users who are voiced in a channel.
 
-Examples:
+    The channels to report or ** for all channels you have joined; if no
+    arguments are given, the users in the active channel will be displayed.
 
-/NAMES
-     - shows nicks in the current channel.
+%9Description:%9
 
-/NAMES -ops #c1,#c2
-     - shows operators in channels #c1 and #c2
+    Displays the users who are in a channel; you can provide multiple channels
+    by separating them with a comma.
 
-See also: WHO, CHANNEL
+%9Examples:%9
+
+    /NAMES -ops
+    /NAMES -voices #irssi,#libera
+
+%9See also:%9 JOIN, PART, WHO, WHOIS
 

docs/help/in/nctcp.in

@@ -1,7 +1,21 @@
 
+%9Syntax:%9
+
 @SYNTAX:nctcp@
 
-Sends a CTCP reply notice to the nick/channel.
+%9Parameters:%9
 
-See also: CTCP, ACTION, MSG, NOTICE
+    A target nickname or channel, a command and the data.
+
+%9Description:%9
+
+    Sends a CTCP reply to a nickname or channel; you can provide multiple
+    targets by separating them with a comma.
+
+%9Examples:%9
+
+    /NCTCP #irssi VERSION King of the Jungle v1.0
+    /NCTCP bob,#libera USERINFO I am bob :p
+
+%9See also:%9 CTCP
 

docs/help/in/netsplit.in

@@ -1,6 +1,16 @@
 
+%9Syntax:%9
+
 @SYNTAX:netsplit@
 
-Irssi keeps track of people who were lost in net splits. With this
-command you can get a list of them.
+%9Description:%9
+
+    Displays some information about users who are currently lost in one or
+    more net splits.
+
+%9Examples:%9
+
+    /NETSPLIT
+
+%9See also:%9 JOIN, LINKS, MAP, PART
 

docs/help/in/network.in

@@ -1,22 +1,70 @@
 
+%9Syntax:%9
+
 @SYNTAX:network@
 
-     -kicks: Maximum number of nicks in one /KICK command
-     -msgs: Maximum number of nicks in one /MSG command
-     -modes: Maximum number of mode changes in one /MODE command
-     -whois: Maximum number of nicks in one /WHOIS command
-     -cmdspeed: Same as /SET cmd_queue_speed, see section 3.1
-     -cmdmax: Same as /SET cmds_max_at_once, see section 3.1
-     -nick, -user, -realname: Specify what nick/user/name to use
-     -host: Specify what host name to use, if you have multiple
-     -usermode: Specify what usermode to use on this network
-     -autosendcmd: Command to send after connecting to a server
-        
-With -autosendcmd argument you can automatically run any commands
-after connecting to network. This is useful for automatically
-identifying yourself to NickServ, for example
+%9Parameters:%9
 
-Shows and changes the settings of defined IRC networks.
+    LIST:            Displays the list of configured networks.
+    ADD:             Adds a network to your configuration.
+    MODIFY:          Modifies a network in your configuration.
+    REMOVE:          Removes a network from your configuration.
 
-See also: CONNECT
+    -nick:           Specifies the nickname to use.
+    -alternate_nick  Specifies the alternate nickname to use.
+    -user:           Specifies the user identity to use.
+    -realname:       Specifies the real name to use.
+    -host:           Specifies the hostname to use.
+    -usermode:       Specifies the user modes to set on yourself.
+    -autosendcmd:    Specifies the commands, separated by the ';' character,
+                     and enclosed within two "'" characters, to perform after
+                     connecting. 
+                     (Some characters need to be escaped - see /help eval)
+    -querychans:     Specifies the maximum number of channels to put in one MODE
+                     or WHO command when synchronizing.
+    -whois:          Specifies the maximum number of nicknames in one WHOIS
+                     command.
+    -msgs:           Specifies the maximum number of nicknames in one PRIVMSG
+                     command.
+    -kicks:          Specifies the maximum number of nicknames in one KICK
+                     command.
+    -modes:          Specifies the maximum number of nicknames in one MODE
+                     command.
+    -cmdspeed:       Specifies the minimum amount of time, expressed in
+                     milliseconds, that the client must wait before sending
+                     additional commands to the server.
+    -cmdmax:         Specifies the maximum number of commands to perform before
+                     starting the internal flood protection.
+    -sasl_mechanism  Specifies the mechanism to use for the SASL authentication.
+                     Irssi supports: PLAIN, EXTERNAL, SCRAM-SHA-1, SCRAM-SHA-256
+                     and SCRAM-SHA-512
+                     Use '' to disable the authentication.
+    -sasl_username   Specifies the username to use during the SASL authentication.
+    -sasl_password   Specifies the password to use during the SASL authentication.
+
+
+    The name of the network to add, edit or remove; if no parameter is given,
+    the list of networks will be displayed.
+
+%9Description:%9
+
+    Displays, adds, modifies or removes the network configuration of IRC
+    networks.
+
+    When using the ADD parameter on a network that already exists, the
+    configuration will be merged with each other.
+
+    We recommend using 'WAIT 2000' between the automated commands in order to
+    prevent you from being kicked from the network due to flooding commands.
+
+%9Examples:%9
+
+    /NETWORK ADD -usermode +giw EFnet
+    /NETWORK ADD -usermode +iw -nick mike -realname 'The one and only mike!' -host staff.irssi.org liberachat
+    /NETWORK ADD -autosendcmd '^MSG NickServ identify WzerT8zq' liberachat
+    /NETWORK ADD -autosendcmd '^MSG Q@CServe.quakenet.org AUTH mike WzerT8zq; WAIT 2000; OPER mike WzerT8zq; WAIT 2000; MODE mike +kXP' Quakenet
+    /NETWORK MODIFY -usermode +gi EFnet
+    /NETWORK REMOVE liberachat
+
+%9See also:%9 CHANNEL, CONNECT, SERVER