John3-16: Page proposed for deletion: Hikari removed from repo [inactive since 2022], depends on outdated wlroots0.15. Note also to that effect under Install Hikari. [May be useful to keep page for some time for those who had installed it; could be left to the discretion of the wiki patroller(s) in due course.] https://gitlab.alpinelinux.org/alpine/aports/-/commit/88455a5c71a548b78dbea7e0cef7adaeba9c6462 ; https://gitlab.alpinelinux.org/alpine/aports/-/commit/d5712a730dc9f156e8d22d762dc655cbf224fa36

2025-09-09T11:55:24Z

Page proposed for deletion: Hikari removed from repo [inactive since 2022], depends on outdated wlroots0.15. Note also to that effect under Install Hikari. [May be useful to keep page for some time for those who had installed it; could be left to the discretion of the wiki patroller(s) in due course.] https://gitlab.alpinelinux.org/alpine/aports/-/commit/88455a5c71a548b78dbea7e0cef7adaeba9c6462 ; https://gitlab.alpinelinux.org/alpine/aports/-/commit/d5712a730dc9f156e8d22d762dc655cbf224fa36

← Older revision		Revision as of 11:55, 9 September 2025
Line 1:		Line 1:
	{{TOC right}}		{{TOC right}}

			{{Delete\|Hikari was removed from the package repos in September 2025. Hikari depends on the outdated [https://gitlab.alpinelinux.org/alpine/aports/-/commit/d5712a730dc9f156e8d22d762dc655cbf224fa36 wlroots0.15].}}



Line 23:		Line 26:

	=== Install Hikari ===		=== Install Hikari ===
			{{Obsolete\|Hikari was removed from the package repos in September 2025. Hikari depends on the outdated [https://gitlab.alpinelinux.org/alpine/aports/-/commit/d5712a730dc9f156e8d22d762dc655cbf224fa36 wlroots0.15].}}

	==== In Alpine Linux [[Edge]] version ====		==== In Alpine Linux [[Edge]] version ====

John3-16: '$' symbol added, as required, to XDG_CONFIG_HOME for touch and chmod instructions and similar.

2025-07-20T06:06:41Z

'$' symbol added, as required, to XDG_CONFIG_HOME for touch and chmod instructions and similar.

← Older revision		Revision as of 06:06, 20 July 2025
Line 56:		Line 56:
	== Configuration ==		== Configuration ==

	To configure Hikari for a given user, one would simply create a <code>hikari.conf</code> file in a <code>hikari</code> folder within the user's <code>XDG_CONFIG_HOME</code> folder. <code>XDG_CONFIG_HOME</code> is an [https://en.wikipedia.org/wiki/Environment_variable environment variable], and it is typically set during Wayland configuration to be the <code>/home/<yourusername>/.config</code> folder. Check, as follows:-		To configure Hikari for a given user, one would simply create a <code>hikari.conf</code> file in a <code>hikari</code> folder within the user's <code>$XDG_CONFIG_HOME</code> folder. <code>XDG_CONFIG_HOME</code> is an [https://en.wikipedia.org/wiki/Environment_variable environment variable], and it is typically set during Wayland configuration to be the <code>/home/<yourusername>/.config</code> folder. Check, as follows:-

	{{Cmd\|$ echo $XDG_CONFIG_HOME}}		{{Cmd\|$ echo $XDG_CONFIG_HOME}}
Line 77:		Line 77:
	Assign only read and write permissions for the user; zero permissions are required for the group and for other users:		Assign only read and write permissions for the user; zero permissions are required for the group and for other users:

	{{Cmd\|$ chmod 600 XDG_CONFIG_HOME/hikari.conf }}		{{Cmd\|$ chmod 600 $XDG_CONFIG_HOME/hikari.conf }}


Line 325:		Line 325:

	<pre>		<pre>
	touch XDG_CONFIG_HOME/hikari/autostart		touch $XDG_CONFIG_HOME/hikari/autostart
	chmod 700 XDG_CONFIG_HOME/hikari/autostart		chmod 700 $XDG_CONFIG_HOME/hikari/autostart
	</pre>		</pre>

John3-16: Created Hikari page on main wiki, including a minor style amendment. Had attempted to move the user sandbox version instead (https://wiki.alpinelinux.org/wiki/User:John3-16/Hikari) but had no 'move' rights. It will be proposed for deletion.

2025-07-20T05:48:21Z

Created Hikari page on main wiki, including a minor style amendment. Had attempted to move the user sandbox version instead (https://wiki.alpinelinux.org/wiki/User:John3-16/Hikari) but had no 'move' rights. It will be proposed for deletion.

New page

{{TOC right}}

{{Pkg|Hikari}} is a [[Wayland|Wayland]] [https://en.wikipedia.org/wiki/Compositing_manager compositor]/[https://en.wikipedia.org/wiki/Window_manager window manager][https://hub.darcs.net/raichoo/hikari heavily inspired] by {{Pkg|cwm}} window manager. It may be considered minimalist by some, installing at 1140 KiB as of July 2025 with no launchbar/taskbar/status bar by default. Supported protocols:-

* {{Pkg|wlroots0.15}}, including [https://wayland.app/protocols/wlr-layer-shell-unstable-v1 layer-shell], [https://wayland.app/protocols/wlr-screencopy-unstable-v1 screencopy] and [https://wayland.app/protocols/wlr-gamma-control-unstable-v1 gamma control].

* [https://specifications.freedesktop.org/wm-spec/latest/ EWMH/NetWM] and [https://en.wikipedia.org/wiki/Inter-Client_Communication_Conventions_Manual ICCCM] standards, in large part, may be reflected while not explicitly stated; for what it's worth, artificial intelligence may quickly be consulted, say, specifically for ten traits of each of these protocols that are demonstrated in Hikari (for example, as per a notable listing by [https://gab.ai Gab AI chat]). On the other hand, however, there are shortcomings: the latest {{pkg|wlroots}} is not supported; {{pkg|wlr-randr}} reports as of July 2025 that the "compositor doesn't support wlr-output-management-unstable-v1"; etc.

This page may act as a quick start only: enough to launch, navigate windows, edit principal configurations, and to demonstrate how to quit Hikari or reload its configuration.

{{Todo| * How to configure for bars, including launch bar and task bar; employing {{Pkg|rofi}} here.
* Elaborate on views, groups, layouts and marks.
Contributions welcome.}}

== Installation ==

=== Install Wayland ===

{{:Wayland}}

=== Install Hikari ===

==== In Alpine Linux [[Edge]] version ====

{{Cmd|$ doas apk add hikari }}

==== In Alpine Linux v3.22 ====

One could consider installing it from the testing repository by first [[Repositories#Using_testing_repository|enabling the testing repo]] and then installing Hikari as follows:

{{Cmd|$ doas apk add hikari@testing }}

==== In subsequent Alpine Linux stable versions ====

Check whether the package has been moved into the 'Community' or 'Main' repositories in your {{pkg|hikari}} package listing: in that link, set the 'Branch' drop-down box to your specific Alpine Linux version. If Hikari appears in the Community repository, ensure that such [[Repositories#Community| repository is enabled]], and then install it as for Edge. Otherwise, consider installing Hikari from @testing repo, as shown for Alpine Linux v3.22.

==== Additional packages ====

As a model, we will consider the case where one would want:-

* {{Pkg|qterminal}} terminal emulator;
* {{Pkg|thunar}} file manager;
* {{Pkg|libreoffice}};
* {{Pkg|chromium}} browser; and
* a handy application launcher like {{Pkg|rofi}}, seeing how there is no launchbar by default. Alpine Linux's '''rofi''' package now supports Wayland, just as [https://github.com/davatorium/rofi rofi's mainline] has, officially, since of 2025.

Substitute throughout for your favorites.

{{Cmd|$ doas apk add qterminal thunar libreoffice chromium rofi}}

== Configuration ==

To configure Hikari for a given user, one would simply create a <code>hikari.conf</code> file in a <code>hikari</code> folder within the user's <code>XDG_CONFIG_HOME</code> folder. <code>XDG_CONFIG_HOME</code> is an [https://en.wikipedia.org/wiki/Environment_variable environment variable], and it is typically set during Wayland configuration to be the <code>/home/<yourusername>/.config</code> folder. Check, as follows:-

{{Cmd|$ echo $XDG_CONFIG_HOME}}

If a blank is returned, one could add the following line to <code>~/.profile</code> file anywhere before any window manager launch lines/code appear towards the end of the file:

export XDG_CONFIG_HOME=$HOME/.config

Create the Hikari configuration folder and copy over the default configuration file to be customised:

<pre>
mkdir $XDG_CONFIG_HOME/hikari
doas cp /etc/hikari/hikari.conf $XDG_CONFIG_HOME/hikari/
</pre>

Give the user (<code>$USER</code>) ownership of the file:

{{Cmd|$ doas chown $USER:$USER $XDG_CONFIG_HOME/hikari/hikari.conf }}

Assign only read and write permissions for the user; zero permissions are required for the group and for other users:

{{Cmd|$ chmod 600 XDG_CONFIG_HOME/hikari.conf }}

=== Configuration file ===

As a quick start, provided that one is okay with Hikari launching with the default/primary display and input settings, then one may not require familiarising oneself nor adding or modifying any of the following stanzas of the configuration file (<code>hikari.conf</code>):-

* <code>ui</code>
* <code>inputs</code> (not currently mentioned in default configuration, anyway)
* <code>outputs</code> (other than changing the <code>background</code> wallpaper path default, if desired)
* <code>layouts</code>
* <code>views</code>

Various 'actions' —such as launching a given application or switching to another window a.k.a. 'view'— will be specified first, so that their shortcuts/'keybindings' could be assigned next.

==== Specify actions to launch terminal(s) ====

* Option 1: Specify default terminal
The default <code>hikari.conf</code> configuration expects one's default terminal emulator to be specified with the <code>TERMINAL</code> environment variable:

<pre>
actions {
terminal = "$TERMINAL"
}
</pre>

To check whether your default terminal is specified:-

{{Cmd|$ echo $TERMINAL }}

If this returns a blank, or if you prefer a different terminal than the one displayed, you can set yours in your <code>.profile</code> file. You may choose one that is optimised for Wayland. In this example, we had installed '''qterminal''', so in the <code>.profile</code> file, before the last line(s), insert:-

<pre>
export TERMINAL=qterminal
</pre>

* Option 2: Specify terminal package(s) in <code>hikari.conf</code>

Edit the <code>actions</code> section, mentioned under Option 1, by changing the predefined <code>terminal</code> action so as to call it, if one wishes, the <code>qterminal</code> action. One could also mention additional terminals, such as {{Pkg|foot}}, as additional actions that could be launched each with their own keybindings, also known as 'shortcuts'. For example:-

<pre>
actions {
qterminal = "/usr/bin/qterminal"
foot = "/usr/bin/foot"
}
</pre>

You may choose to specify the package's path, as shown, in case that this could enhance security.

==== Specify other actions ====

One could further instruct Hikari what other essential actions one would want to launch with keybindings/shortcuts that will be soon specified. For example, continue the above passage as follows:-

<pre>
actions {
qterminal = "/usr/bin/qterminal"
foot = "/usr/bin/foot"
libreoffice = "/usr/bin/libreoffice"
chromium = "/usr/bin/chromium"
thunar = "/usr/bin/thunar"
rofi = "/usr/bin/rofi -combi-modi run,drun,filebrowser -show combi -sort"

}
</pre>

{{Tip|The '''rofi''' arguments proposed above will offer a useful "combination" of modes: the default '''rofi''' view that would appear with those arguments is the combi-mode that will search for any command in your <code>$PATH</code> as you type it into '''rofi''', and it will simultaneously also search for that command among the <code>$XDG_DATA_HOME/applications</code> as well as files with .desktop file extensions in <code>$XDG_DATA_DIRS/applications</code>. Furthermore, with those '''rofi''' specified command switches, one could alternatively hit <Ctr>+<Tab> to toggle between the run or drun modes only; or toggle into its filebrowser, from where one could navigate to any file and then hit <Return> to open the file with its assigned mime application. '''Rofi''' may therefore replace a launch bar. }}

Add other commands to that <code>actions</code> stanza that one would want to make application shortcuts/'keybindings' for.

==== Specify custom keybindings ====

Now, continuing in <code>hikari.conf</code>, navigate just below that <code>actions</code> stanza to the <code>bindings</code> stanza, and put your cursor at the <code>action-terminal</code> keybinding.

Note that Hikari syntax requires for each of the aforementioned actions to be referred to in this keybindings stanza with the <code>action-</code> prefix; for example, the <code>terminal</code> action is to being referred to here as <code>action-terminal</code>.

<pre>
bindings {
keyboard {

[...]

"L+Return" = action-terminal

[...]

}
</pre>

Note what the available key codes are, from the Hikari [https://hub.darcs.net/raichoo/hikari/browse/share/man/man1/hikari.md man page]:-

L = <Logo>
S = <Shift>
C = <Control>
A = <Alt>
5 = <AltGR>

Therefore, the default keybinding/shortcut to launch the original terminal (<code>action-terminal</code>) defined above is: <Logo>+<Return> .

One might want to replace the <Logo>+<Return> keybinding with perhaps the more familiar <Ctr>+<Alt>+<Return> binding, say.

{{Tip| It is important to check that one's chosen keybinding combination has not already been assigned in <code>hikari.conf</code>. }}

<Ctr>+<Alt>+<key> is not bound to anything by default in Hikari as of July 2025. Add your chosen <key> combination for each of the shortcuts for the <code>actions</code> that you defined earlier. say, <Ctr>+<Alt>+<Return> could be used to launch the <code>action-qterminal</code>, as opposed to the original and default <code>action-terminal</code> action. Continue assigning keybindings for the other actions also:

<pre>
bindings {
keyboard {

[...]
"CA+Return" = action-qterminal
"CA+f" = action-foot
"CA+l" = action-libreoffice
"CA+c" = action-chromium
"CA+t" = action-thunar
"CA+r" = action-rofi
[...]

}
</pre>

The <code>[...]</code> here only represent unrelated passages from that stanza.

Change any other keybindings, if so wished. One may even assign additional (albeit redundant) shortcuts in that stanza for the same aforementioned actions, as long as the chosen keybinding hasn't already been assigned for a different action, of course, which would create a confusion for that keybinding. Say, for '''rofi''', the <code>action-rofi</code> launch instruction could alternatively be executed through the following additional <code>action-rofi</code> keybinding line that is the same as, say, the shortcut <Logo>+<d> used in '''cwm''':

<pre>
"L+d" = action-rofi
</pre>

==== Bindings to toggle between windows/views ====

The <code>view-cycle-next</code> keybinding (and <code>view-cycle-prev</code>) is another essential binding to make note of in order to navigate between any view/window that one may launch:

<pre>
bindings {
keyboard {

[...]
"LS+n" = view-cycle-next
"LS+p" = view-cycle-prev

[...]

}
</pre>

One may choose to change these to something such as the following.

<pre>
bindings {
keyboard {

[...]
"L+Tab" = view-cycle-next
"LS+Tab"= view-cycle-prev
[...]

}
</pre>

{{Tip| Be advised that the <code>view-cycle-prev</code> action may need to involve the <Shift> key plus the same key(s) as with <code>view-cycle-next</code>, as opposed to trying unrelated keys; your mileage may vary. }}

==== Bindings to toggle between ttys ====

In case Hikari is launched from the default tty1 login and one's configuration does not work as expected and then hopes to edit the configuration file by logging in from a different tty (a.k.a. [https://en.wikipedia.org/wiki/Virtual_console virtual terminal] or vt), be aware that the common <Ctr>+<Alt>+<Fn> combination shortcut, e.g. <Ctr>+<Alt>+<F2> for tty2, does not work in the default configuration. Instead, <Alt>+<Fn> changes to different ttys e.g. <Alt>+<F2> for tty2, as per the default bindings:-

<pre>
bindings {
keyboard {

[...]

"A+F1" = vt-switch-to-1
"A+F2" = vt-switch-to-2
[...]

}
</pre>

One might decide to change that <code>hikari.conf</code> keybinding passage (for <code>vt-switch-to-1</code> through <code>vt-switch-to-9</code>) to the <Ctr>+<Alt>+<Fn> bindings that one may be used to; the following binding choices are not assigned elsewhere in Hikari as of July 2025:

"CA+F1" = vt-switch-to-1
"CA+F2" = vt-switch-to-2
"CA+F3" = vt-switch-to-3
"CA+F4" = vt-switch-to-4
"CA+F5" = vt-switch-to-5
"CA+F6" = vt-switch-to-6
"CA+F7" = vt-switch-to-7
"CA+F8" = vt-switch-to-8
"CA+F9" = vt-switch-to-9

==== Specify session keybindings ====

Be mindful to make note of these further important keybindings and/or to edit them to suit your preferences:-

* Lock your screen (<Logo>+<Space>+<Backspace>).
* Quit your Hikari session (<Logo>+<Control>+<LeftAlt>+<nowiki><q></nowiki>); which will either (a) drop one into a tty virtual terminal; or (b) if there is no display manager, it may log one out.
* Reload your Hikari configuration (<Logo>+<Control>+<LeftAlt>+<r>), in case one wants to attempt applying any recent edits in <code>hikari.conf</code> during that same session.

<pre>
bindings {
keyboard {

[...]

"LS+Backspace" = lock
"LCA+q" = quit
"LCA+r" = reload

[...]

</pre>

==== Specify mouse bindings ====

The default <code>hikari.conf</code> only specifies the following mouse bindings at the time of creation of this wiki:

<pre>
mouse {
"L+left" = mode-enter-move
"L+right" = mode-enter-resize
}
</pre>

As per Hikari's man page, available mouse button actions are: ""right", "middle", "left", "side", "extra", "forward", "back" and "task"."

One may prefer to carry over, say, certain {{Pkg|cwm}} mouse bindings instead, if these were more familiar, including:

<pre>
mouse {
"A+left" = mode-enter-move
# For the following, apply keys and drag the lower right corner of the window
"A+middle"= mode-enter-resize
}
</pre>

=== Autostarting session applications ===

All applications or instructions that one would like to start automatically during a particular user's session can be specified in the <code>autostart</code> file that could be created in Hikari's configuration folder for the user; only read, write and execution permissions for the user are required:

<pre>
touch XDG_CONFIG_HOME/hikari/autostart
chmod 700 XDG_CONFIG_HOME/hikari/autostart
</pre>

In that <code>autostart</code> file, there is no need for a [https://en.wikipedia.org/wiki/Shebang_(Unix) shebang line] (<code>#!</code>, <code>#!/bin/sh</code>, etc) anywhere. Place [[BusyBox]]/{{pkg|ash}} commands on each line in that file, placing ampersands (<code>&</code>) at the end of each command line (similarly to X11's <code>.xinitrc</code> file). In a text editor, enter, for example:-

/usr/bin/qterminal &
/usr/bin/libreoffice &
/usr/bin/rofi -combi-modi run,drun,filebrowser -show combi -sort &

=== Theming / Ricing ===

The following will model theming to Breeze Dark.

{{Cmd|$ doas apk add gsettings-desktop-schemas breeze-gtk breeze-icons qt6ct }}

==== GTK applications ====
* LXAppearance method - Install {{Pkg|lxappearance}} (may only be in edge's @testing repository) and set 'Breeze-Dark' under Widgets; and 'Breeze Dark' under Icons theme.

* Gsettings method - In a shell:

<pre>
gsettings set org.gnome.desktop.interface gtk-theme 'Breeze-Dark'
gsettings set org.gnome.desktop.interface icon-theme 'breeze-dark'
</pre>

==== Qt applications ====
: Qt applications may be themed in part with the GTK applications instruction above. One application could be suggested for installation: {{Pkg|qt6ct}} (may only be in edge's @testing repository), although other approaches exist. One may also need to add the following in <code>~/.profile</code> before any wm/compositor launch line or code:-

export QT_QPA_PLATFORMTHEME=qt6ct

: Launch {{Pkg|qt6ct}}. Under the Appearance tab, select 'Breeze-Dark'.

== Launch Hikari ==

{{Tip| Before launching Hikari, make a hard copy of all essential keybindings —'''especially those addressed in the [[Hikari#Configuration|Configuration]] section above'''— to have a listing of the shortcuts needed to launch and navigate through your applications, seeing how there are no out-of-the-box launchbars or taskbars.}}

=== From a display manager ===

Consult how to configure your [https://en.wikipedia.org/wiki/X_display_manager 'dm'] from among Alpine Linux's [[Display_manager|display managers]].

=== From a tty/virtual terminal ===

In layman's terms, if on startup you do not have a graphical interface login, known as a display manager, but rather a 'teletype' login, you could simply enter the following.

* Option 1 - Note: Do not do so when running as root, for security reasons.

{{Cmd|$ exec /usr/bin/dbus-run-session /usr/bin/hikari }}

* Option 2 - A useful launch alternative is to have Hikari automatically log configuration errors and various other session errors/warnings into a log file, say, into <code>~/hikariandsessionerrors.log</code>. This could help in troubleshooting, say, from a different tty; the log will be overwritten for each session:

{{Cmd|$ exec /usr/bin/dbus-run-session /usr/bin/hikari 2> ~/hikariandsessionerrors.log }}

* Option 3 - If you prefer to keep the error log files of each session, consider adding date and time stamps instead:

{{Cmd|$ exec /usr/bin/dbus-run-session /usr/bin/hikari 2> ~/hikariandsessionerrors-$(date +'%d.%m.%Y_at_%Hh.%Mmns').log }}

=== Autostarting without a graphical display manager ===

Three options:-

* You could add the above instruction to the bottom of your <code>/home/<yourusername>/.profile</code>, but before any other window manager launcher instruction there. However, the following option could be preferable.

* In case you would only want to launch Hikari from the default tty1 so as to be able to use any other available tty (tty2-tty6) to edit your Hikari configuration if that session is hanging/crashing, then consider using the following code instead:

<pre>
if [ "$(tty)" = "/dev/tty1" ]; then
exec /usr/bin/dbus-run-session /usr/bin/hikari 2> ~/hikariandsessionerrors.log }}
fi
</pre>

* Alternatively, at the end of <code>.profile</code>, edit code, if any, that determines, depending on any user input, what compositor/window manager to launch: consider employing the code or launch line from any of the options above.

== Navigating a Hikari session ==

Launch applications:-
* from your defined action keybinding/shortcuts; or
* from your terminal, launched from your autostart file, or launched from your keybinding; or
* from '''rofi''' or any other application launcher that you may have installed and launched using its keybinding/shortcut; or
* from a launchbar that you may install and configure.

=== Indicator bars ===
When you focus a view (or program 'window', so to speak) and then click on the <Logo> key (a.k.a. the 'Super'/'Window'/'Command' key), then 'indicator bars' will light up in yellow, pink, etc. on the top left of the view; the colors can be programmed to indicate the state of each view (see colorscheme in Hikari's man page).

* Consider Example (a):
** The first bar displays the title of the window e.g. 'New Tab - Chromium'
** The second bar, below it, may look like: 0 - HDMI-A-1;
*** The first number, the 0, refers to the sheet number,
*** The second part of the ID reports the display output, indicating in this case that it is connected via "HDMI". See how this corresponds to the monitor's display name as reported, say, by {{pkg|xrandr}} or {{pkg|arandr}}, although more Wayland-specific applications could be used, preferably. That indicator bar would also display any 'mark' that you may have given for the view.
** The third bar displays the name of the package's title or, if any is assigned, the name of its group. Group names can be given for each application by developing the 'views' stanzas in <code>hikari.conf</code>: browser, editor, etc.

* Consider Example (b):
: Depending on your configuration, the second indicator bar may state, for example, 0 @ 1 - HDMI-A-1 instead. In this case, a second number appears after an @ symbol, such as @ 1, which indicates 'output number 1'. Output numbers can be assigned for specific packages in your <code>hikari.conf</code> file.

Note that, according to Hikari's man page, "Views that are a member of sheet 0 will always be visible but stacked below the views of the selected sheet." This may not be necessarily noticeable, but if this is not desired, one could, for example, create a stanza for each affected package under the <code>views</code> section and specify for those packages to be launched under <code>sheet = 1</code> instead. Concurrently, if desired, one could also specify a group name for the package. For example:

<pre>
views {
chromium = {
sheet = 1
group = browser
}

[...]

}
</pre>

== See also ==

* [https://hub.darcs.net/raichoo/hikari Hikari upstream] - README, upstream issues.
* [[Installation#Post-Installation|Post Installation]].
* [[Wayland|Wayland]].
* [https://hub.darcs.net/raichoo/hikari/browse/share/man/man1/hikari.md Hikari man page upstream.]
* [https://docs.freebsd.org/en/books/handbook/wayland/#wayland-hikari Hikari FreeBSD Handbook - Hikari section.]
* [http://hikari.acmelabs.space/ Hikari - Overview of various protocols, community sites.]
* [https://www.youtube.com/watch?v=oIXYFwKx-LU Hikari introductory video by "raichoo", Hikari maintainer], also found in [http://hikari.acmelabs.space/ webpage] mentioned directly above.
* [https://aur.archlinux.org/packages/hikari-darcs Hikari AUR package on Arch.]

[[Category:Compositor]]
[[Category:Window Managers]]

Hikari - Revision history

John3-16: '$' symbol added, as required, to XDG_CONFIG_HOME for touch and chmod instructions and similar.

John3-16: Created Hikari page on main wiki, including a minor style amendment. Had attempted to move the user sandbox version instead (https://wiki.alpinelinux.org/wiki/User:John3-16/Hikari) but had no 'move' rights. It will be proposed for deletion.