File riverguile-0.1.0+git8.obscpio of Package riverguile
07070100000000000081A400000000000000000000000165A4F7D200000029000000000000000000000000000000000000002100000000riverguile-0.1.0+git8/.gitignoreprotocol/*.c
protocol/*.h
*.o
riverguile
07070100000001000081A400000000000000000000000165A4F7D20000894D000000000000000000000000000000000000001E00000000riverguile-0.1.0+git8/LICENSE GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<https://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<https://www.gnu.org/licenses/why-not-lgpl.html>.
07070100000002000081A400000000000000000000000165A4F7D20000067C000000000000000000000000000000000000001F00000000riverguile-0.1.0+git8/MakefileSCANNER := wayland-scanner
PREFIX=/usr/local
BINDIR=$(PREFIX)/bin
DATADIR=$(PREFIX)/share
MODULEDIR=$(DATADIR)/guile/3.0
MANDIR=$(DATADIR)/man
CFLAGS=-g -Wall -Werror -Wextra -Wpedantic -Wno-unused-parameter $\
-Wno-overlength-strings -Wformat-security -Wformat -Wunused-result $\
-I protocol $\
$(shell pkg-config --cflags wayland-client) $\
$(shell guile-config compile)
LIBS=-lrt $\
$(shell pkg-config --libs wayland-client) $\
$(shell guile-config link)
OBJ=src/riverguile.o $\
src/seat.o src/output.o $\
src/call-layout-demand-handler.o $\
src/call-user-command-handler.o $\
src/call-idle-handler.o $\
src/call-exit-handler.o $\
src/load-script.o $\
protocol/river-layout-v3.o $\
protocol/ext-idle-notify-v1.o $\
protocol/river-control-unstable-v1.o
GEN=protocol/river-layout-v3.c protocol/river-layout-v3.h $\
protocol/ext-idle-notify-v1.c protocol/ext-idle-notify-v1.h $\
protocol/river-control-unstable-v1.c protocol/river-control-unstable-v1.h
all: riverguile
riverguile: $(OBJ)
$(CC) $(LDFLAGS) -g -o $@ $(OBJ) $(LIBS)
$(OBJ): $(GEN)
%.c: %.xml
$(SCANNER) private-code < $< > $@
%.h: %.xml
$(SCANNER) client-header < $< > $@
install: riverguile
install -D riverguile $(DESTDIR)$(BINDIR)/riverguile
install -m 644 -D doc/riverguile.1 $(DESTDIR)$(MANDIR)/man1/riverguile.1
install -m 644 -D module/riverguile.scm $(DESTDIR)$(MODULEDIR)/riverguile.scm
uninstall:
$(RM) $(DESTDIR)$(BINDIR)/riverguile
$(RM) $(DESTDIR)$(MANDIR)/man1/riverguile.1
$(RM) $(DESTDIR)$(MODULEDIR)/riverguile.scm
clean:
$(RM) riverguile
$(RM) $(GEN)
$(RM) $(OBJ)
$(RM) $(IMG)
.PHONY: clean install uninstall all
07070100000003000081A400000000000000000000000165A4F7D200000913000000000000000000000000000000000000002000000000riverguile-0.1.0+git8/README.md# riverguile
Scripting layer for the [river](https://github.com/riverwm/river) Wayland
server using [Guile Scheme](https://www.gnu.org/software/guile/). Send commands
to river and install handlers for various events, including layout demands.
The ultimate aim of giverguile is to allow comfortable scripting in the context
of desktop operations, including window management.
> "So, the UNIX philosophy is nice and all, but I wish I could script my desktop
> in a way that's a bit more integrated and less hacky."
Do you agree with that statement? Do you like Lisp / Scheme? Do you believe
policy over mechanism is the only sane way to design a scripting API? Then
riverguile might be what you want!
Riverguile follows river development closely, exposing new functionality as
scheme procedures and advocating for even more scripting features. Right now,
riverguile is implemented as an interpreter for river init scripts.
```scheme
#!/bin/env riverguile
!#
(use-modules (riverguile))
;; Lock the screen after five minutes and darken the screen.
(install-handler 'idle:300 (lambda (event)
(cond ((eq? event 'idle) (system "swaylock &")
(system "backlight.sh set-to 40"))
((eq? event 'resume) (system "backlight.sh set-to 100")))))
(define split 0.55)
(define (layout:rows n x y w h)
(letrec ((height (/ h n))
(rows (lambda (n)
(if (eq? n 0)
'()
(let ((Y (- (+ y h) (* n height))))
(append (list (list x Y w height))
(rows (- n 1))))))))
(rows n)))
(define (layout:split n x y w h)
(if (eq? n 1)
(list (list x y w h))
(letrec* ((left (* split w))
(right (- w left)))
(append (list (list x y left h))
(layout:rows (- n 1) (+ x left) y right h)))))
;; Replicate rivertile.
(R default-layout riverguile)
(install-handler 'layout-demand (lambda (view-count width height tags output)
(layout:split view-count 0 0 width height)))
```
07070100000004000041ED00000000000000000000000265A4F7D200000000000000000000000000000000000000000000001A00000000riverguile-0.1.0+git8/doc07070100000005000081A400000000000000000000000165A4F7D2000024CA000000000000000000000000000000000000002700000000riverguile-0.1.0+git8/doc/riverguile.1.TH RIVERGUILE 1 2024-01-13 "git.sr.ht/~leon_plickat/riverguile" "General Commands Manual"
.
.SH NAME
.P
riverguile \- scheme powered scripting layer for river
.
.
.SH SYNOPSIS
.SY riverguile
path-to-script
.YS
.
.
.SH DESCRIPTION
.P
Scripting layer for the
.BR river (1)
Wayland server.
Allows the user to send commands to the Wayland server (probably river) and
install handlers for events from a scheme script.
The scheme implementation is provided by
.BR guile (1).
.P
The canonical way to use riverguile is as an interpreter for the river init
script.
To do so place the following expression at the very top of your init script:
.P
.RS
.EX
#!/bin/env riverguile
!#
.EE
.RE
.P
Do not leave out the second line, as the octothorpe plus exclamation-mark
combination indicates a multi-line comment in scheme.
Do not forget to mark your init script as executable.
Your custom scheme code to configure the river session may follow after these
two lines.
.P
By default, riverguile will exit after the script has been loaded.
However if certain handlers are installed it will run continuously to provide
that functionality.
.
.
.SH COMMANDS
.P
Riverguile exposes the special procedure
\fB(riverctl \fR\fIfirst\fR . \fIrest\fR\fB)\fR, which can be used to send
commands to the server in a similar fashion to
.BR riverctl (1).
All arguments must be strings.
.P
Here is an example of using this procedure to instruct river to spawn an
instance of the
.BR foot (1)
terminal emulator:
.P
.RS
.EX
(\fBriverctl\fR "spawn" "foot")
.EE
.RE
.P
Riverguile also provides a scheme module which exports macros that wrap this
procedure in a more ergonomic interface.
This module is documented in the \fBRIVERGUILE MODULE\fR section of this
document.
.
.
.SH EVENT HANDLERS
.P
Riverguile exposes the special procedure
\fB(install-handler \fR\fIkey\fR \fIproc\fR\fB)\fR, which can be used to install
event handlers.
The parameter \fIkey\fR is a symbol indicating for which event to install
the procedure \fIproc\fR.
The following keys are currently available:
.
.P
\fBlayout-demand\fR
.P
.RS
Installing a handler for this key allows the user to provide window layouts.
All limitations of the river-layout-v3 protocol apply.
The server will trigger this event when a new layout is required ("demanded").
.P
Installing a layout-demand handler will cause riverguile to run continuously.
.P
The handler procedure must accept five required arguments, which are, in order:
The amount of views in the layout (integer), the available width (integer), the
available height (integer), the currently active tag set (integer representing a
bitfield of size 32) and the global name of the output the layout is needed for
(integer).
The procedure must return a list containing exactly as many lists as there are
views in the layout.
Each of those sublists must contains exactly four numerical values, which are
the x and y coordinates of the window as well as its width and height.
Window positions and dimensions get applied to the window list top to bottom.
.P
Note that the numerical values do not need to be exact, riverguile takes care
of rounding and casting for you.
.P
Here is an example of a simple layout-demand handler which simply makes all
windows use all available space:
.P
.RS
.EX
(\fBinstall-handler\fR 'layout-demand
(\fBlambda\fR (view-count width height tags output)
(\fBletrec\fR ((iter (\fBlambda\fR (n)
(if (eq? 0 n)
'()
(\fBappend\fR (\fBlist\fR (\fBlist\fR 0 0 width height))
(iter (1- n)))))))
(iter view-count))))
.EE
.RE
.RE
.
.P
\fBuser-command\fR
.P
.RS
User commands are intended to allowing the user to update parameters of the
layout live.
The user sends a command - a string - to the server, which relays is to the
layout generator.
Of course, nothing is stopping you from (ab-)using this event to trigger
arbitrary scheme code on key presses or on outside events, or from simply not
using it at all.
Please see
.BR riverctl (1)
regarding how to send user commands and how to configure the server to send them
on key presses (note that usage of the riverctl executable maps one-to-one to
the usage of the riverguile procedure of the same name).
After a user-command has been received, the server will trigger a layout-demand
if there are visible windows.
.P
Installing a user-command handler will \fInot\fR cause riverguile to run continuously.
This event is an extension to the layout-demand event and as such it is invalid
to install a user-command handler without also installing a layout-demand
handler.
.P
The handler procedure must accept three arguments, which are, in order:
The command (string), the currently active tags (integer representing a
bitfield of size 32) and the global name of the output (integer).
.P
Here is an example of a simple user-command handler which simply evaluates the
string as scheme code:
.P
.RS
.EX
(\fBinstall-handler\fR 'user-command
(\fBlambda\fR (cmd tags output)
(\fBeval-string\fR cmd)))
.EE
.RE
.P
Note that this is not necessarily good practice, but serves as a decent example.
.RE
.
.P
\fBidle:X\fR
.P
.RS
A handler installed for this key will be triggered after the system has been
idle for \fIX\fR seconds and once more once the system is no longer idle.
.P
Installing an idle handler will cause riverguile to run continuously.
Multiple idle handlers can be installed.
.P
Idle state is server policy and may depend on a multitude of factors, but
usually maps directly to the usage activity of input devices by the user.
Certain programs may inhibit idle state, like for example video players.
.P
The handler procedure must accept one argument, a symbol indicating the type
of idle event.
This symbol is either \fBidle\fR, indicating the system has been idle for the
configured amount of time, or \fBresume\fR, indicating that the system is no
longer idle.
.P
Here is an example which will dim the screen after two minutes of inactivity
and lock it after five:
.P
.RS
.EX
(\fBinstall-handler\fR 'idle:120
(\fBlambda\fR (event)
(\fBcond\fR ((\fBeq?\fR event 'idle) (riverctl "spawn" "light -S 20"))
((\fBeq?\fR event 'resume) (riverctl "spawn" "light -S 100")))))
(\fBinstall-handler\fR 'idle:300
(\fBlambda\fR (event)
(if (\fBeq?\fR event 'idle) (riverctl "spawn" "swaylock"))))
.EE
.RE
.P
Note: All idle events relate to the first advertised seat.
As of now, river only supports a single seat anyway.
.RE
.
.P
\fBexit\fR
.RE
.RS
This key allows you to installs a handler which is called when riverguile exits.
.P
The procedure takes no arguments.
.P
Here is an example which adds a message to the system log on exit:
.P
.RS
.EX
(\fBinstall-handler\fR 'exit
(\fBlambda\fR ()
(riverctl "spawn" "logger 'goodbye from riverguile'")))
.EE
.RE
.RE
.
.
.SH RIVERGUILE MODULE
.P
A complete installation of riverguile also provides a scheme module which
exposes macros and procedures with the intention of exposing more ergonomic
interfaces.
.P
.RS
.EX
(\fBuse-modules\fR (riverguile))
.EE
.RE
.P
This module is not necessary to use riverguile and also will not provide any
of riverguiles functionality to any scheme script not executed by riverguile.
.P
The following documents all exported procedures and macros.
.
.P
(\fBR\fR \fIarg\fR ...)
.P
.RS
A direct wrapper for the \fBriverctl\fR procedure, however it also accepts
symbols and numbers in addition to strings.
Any expressions you need evaluated must be unquoted.
.P
.RS
.EX
(R spawn foot)
(R spawn "notify-send hello")
(\fBfor-each\fR (\fBlambda\fR (cmd) (R spawn ,cmd))
'("foot" "firefox" "nautilus"))
.EE
.RE
.RE
.
.P
(\fBR:map\fR \fImode\fR (\fImod\fR \fIkey\fR \fIcmd\fR ...) ...)
.P
.RS
This macro is intended to simplify defining keymaps.
Please refer to the
.BR riverctl (1)
manual page for more details and specifics regarding rivers map mechanism.
Any expressions you need evaluated must be unquoted.
.P
.RS
.EX
(R:map normal
(Super H focus-view left)
(Super Space spawn foot)
(-repeat None XF86AudioRaiseVolume spawn "volume.sh raise 5%"))
(\fBfor-each\fR (\fBlambda\fR (mode)
(R:map ,mode
(None XF86MonBrightnessUp spawn "light -A 5")
(None XF86MonBrightnessDown spawn "light -U 5")))
'("normal" "locked"))
.EE
.RE
.RE
.
.P
(\fBR:input\fR \fIname\fR (\fIval\fR \fIvar\fR ...) ...)
.P
.RS
This macro is intended to simplify input device configuration.
Please refer to the
.BR riverctl (1)
manual page for details and specifics regarding the input device configuration.
Any expressions you need evaluated must be unquoted.
.P
.RS
.EX
(R:input pointer-1149-4128-Kensington_Expert_mouse
(accel-profile none)
(pointer-accel 0.6)
(scroll-method button)
(scroll-button BTN_SIDE))
.EE
.RE
.RE
.
.P
(\fBR:keyboard-group\fR \fIname\fR . \fIdevices\fR)
.P
.RS
This macro is intended to simplify creation of keyboard groups.
Please refer to the
.BR riverctl (1)
manual page for details and specifics regarding keyboard groups.
Any expressions you need evaluated must be unquoted.
.P
.RS
.EX
(R:keyboard-group split
keyboard-XXXX-XXXX-Device-1
keyboard-XXXX-XXXX-Device-2
keyboard-XXXX-XXXX-Device-3)
.EE
.RE
.RE
.
.
.SH SEE ALSO
.BR river (1),
.BR riverctl (1),
.BR rivertile (1),
.BR guile (1)
.
.
.SH AUTHOR
.P
.MT leonhenrik.plickat@stud.uni-goettingen.de
Leon Henrik Plickat
.ME
07070100000006000041ED00000000000000000000000265A4F7D200000000000000000000000000000000000000000000001D00000000riverguile-0.1.0+git8/module07070100000007000081A400000000000000000000000165A4F7D200000922000000000000000000000000000000000000002C00000000riverguile-0.1.0+git8/module/riverguile.scm;;;
;;; This file if part of riverguile, the scheme powered scripting layer for
;;; the river Wayland desktop.
;;;
;;; Copyright (C) 2024 Leon Henrik Plickat <leonhenrik.plickat@stud.uni-goettingen.de>
;;;
;;; This library is free software; you can redistribute it and/or
;;; modify it under the terms of the GNU Lesser General Public
;;; License version 3 as published by the Free Software Foundation.
;;;
;;; This library is distributed in the hope that it will be useful,
;;; but WITHOUT ANY WARRANTY; without even the implied warranty of
;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
;;; Lesser General Public License for more details.
;;;
;;; You should have received a copy of the GNU Lesser General Public
;;; License along with this library; if not, write to the Free Software
;;; Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
;; This module provides helper macros and procedures for riverguile and will not
;; be useful in any other context. The contents of this module are documented
;; in the riverguile.1 manual page.
(define-module (riverguile)
#:export (R
R:input
R:map
R:keyboard-group))
(define (stringify x)
(cond ((string? x) x)
((number? x) (number->string x))
((symbol? x) (symbol->string x))))
(define-syntax R
(syntax-rules ()
((R arg ...)
(apply riverctl
(map stringify `(arg ...))))))
(define-syntax R:map
(syntax-rules ()
((R:map mode (mod key cmd ...) ...)
(for-each (lambda (args)
(apply riverctl
(map stringify
(append `(map mode) args))))
`((mod key cmd ...) ...)))))
(define-syntax R:input
(syntax-rules ()
((R:input name (val var ...) ...)
(for-each (lambda (args)
(apply riverctl
(map stringify
(append `(input name) args))))
`((val var ...) ...)))))
(define-syntax R:keyboard-group
(syntax-rules ()
((R:keyboard-group name . devices)
(let ((N (stringify 'name))
(D (map stringify 'devices)))
(riverctl "keyboard-group-create" N)
(for-each (lambda (d)
(riverctl "keyboard-group-add" N d))
D)))))
07070100000008000041ED00000000000000000000000265A4F7D200000000000000000000000000000000000000000000001F00000000riverguile-0.1.0+git8/protocol07070100000009000081A400000000000000000000000165A4F7D2000011AA000000000000000000000000000000000000003600000000riverguile-0.1.0+git8/protocol/ext-idle-notify-v1.xml<?xml version="1.0" encoding="UTF-8"?>
<protocol name="ext_idle_notify_v1">
<copyright>
Copyright © 2015 Martin Gräßlin
Copyright © 2022 Simon Ser
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice (including the next
paragraph) shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
</copyright>
<interface name="ext_idle_notifier_v1" version="1">
<description summary="idle notification manager">
This interface allows clients to monitor user idle status.
After binding to this global, clients can create ext_idle_notification_v1
objects to get notified when the user is idle for a given amount of time.
</description>
<request name="destroy" type="destructor">
<description summary="destroy the manager">
Destroy the manager object. All objects created via this interface
remain valid.
</description>
</request>
<request name="get_idle_notification">
<description summary="create a notification object">
Create a new idle notification object.
The notification object has a minimum timeout duration and is tied to a
seat. The client will be notified if the seat is inactive for at least
the provided timeout. See ext_idle_notification_v1 for more details.
A zero timeout is valid and means the client wants to be notified as
soon as possible when the seat is inactive.
</description>
<arg name="id" type="new_id" interface="ext_idle_notification_v1"/>
<arg name="timeout" type="uint" summary="minimum idle timeout in msec"/>
<arg name="seat" type="object" interface="wl_seat"/>
</request>
</interface>
<interface name="ext_idle_notification_v1" version="1">
<description summary="idle notification">
This interface is used by the compositor to send idle notification events
to clients.
Initially the notification object is not idle. The notification object
becomes idle when no user activity has happened for at least the timeout
duration, starting from the creation of the notification object. User
activity may include input events or a presence sensor, but is
compositor-specific. If an idle inhibitor is active (e.g. another client
has created a zwp_idle_inhibitor_v1 on a visible surface), the compositor
must not make the notification object idle.
When the notification object becomes idle, an idled event is sent. When
user activity starts again, the notification object stops being idle,
a resumed event is sent and the timeout is restarted.
</description>
<request name="destroy" type="destructor">
<description summary="destroy the notification object">
Destroy the notification object.
</description>
</request>
<event name="idled">
<description summary="notification object is idle">
This event is sent when the notification object becomes idle.
It's a compositor protocol error to send this event twice without a
resumed event in-between.
</description>
</event>
<event name="resumed">
<description summary="notification object is no longer idle">
This event is sent when the notification object stops being idle.
It's a compositor protocol error to send this event twice without an
idled event in-between. It's a compositor protocol error to send this
event prior to any idled event.
</description>
</event>
</interface>
</protocol>
0707010000000A000081A400000000000000000000000165A4F7D200000E83000000000000000000000000000000000000003D00000000riverguile-0.1.0+git8/protocol/river-control-unstable-v1.xml<?xml version="1.0" encoding="UTF-8"?>
<protocol name="river_control_unstable_v1">
<copyright>
Copyright 2020 The River Developers
Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
</copyright>
<interface name="zriver_control_v1" version="1">
<description summary="run compositor commands">
This interface allows clients to run compositor commands and receive a
success/failure response with output or a failure message respectively.
Each command is built up in a series of add_argument requests and
executed with a run_command request. The first argument is the command
to be run.
A complete list of commands should be made available in the man page of
the compositor.
</description>
<request name="destroy" type="destructor">
<description summary="destroy the river_control object">
This request indicates that the client will not use the
river_control object any more. Objects that have been created
through this instance are not affected.
</description>
</request>
<request name="add_argument">
<description summary="add an argument to the current command">
Arguments are stored by the server in the order they were sent until
the run_command request is made.
</description>
<arg name="argument" type="string" summary="the argument to add"/>
</request>
<request name="run_command">
<description summary="run the current command">
Execute the command built up using the add_argument request for the
given seat.
</description>
<arg name="seat" type="object" interface="wl_seat"/>
<arg name="callback" type="new_id" interface="zriver_command_callback_v1"
summary="callback object"/>
</request>
</interface>
<interface name="zriver_command_callback_v1" version="1">
<description summary="callback object">
This object is created by the run_command request. Exactly one of the
success or failure events will be sent. This object will be destroyed
by the compositor after one of the events is sent.
</description>
<event name="success" type="destructor">
<description summary="command successful">
Sent when the command has been successfully received and executed by
the compositor. Some commands may produce output, in which case the
output argument will be a non-empty string.
</description>
<arg name="output" type="string" summary="the output of the command"/>
</event>
<event name="failure" type="destructor">
<description summary="command failed">
Sent when the command could not be carried out. This could be due to
sending a non-existent command, no command, not enough arguments, too
many arguments, invalid arguments, etc.
</description>
<arg name="failure_message" type="string"
summary="a message explaining why failure occurred"/>
</event>
</interface>
</protocol>
0707010000000B000081A400000000000000000000000165A4F7D2000024EB000000000000000000000000000000000000003300000000riverguile-0.1.0+git8/protocol/river-layout-v3.xml<?xml version="1.0" encoding="UTF-8"?>
<protocol name="river_layout_v3">
<copyright>
Copyright 2020-2021 The River Developers
Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
</copyright>
<description summary="let clients propose view positions and dimensions">
This protocol specifies a way for clients to propose arbitrary positions
and dimensions for a set of views on a specific output of a compositor
through the river_layout_v3 object.
Layouts are a strictly linear list of views, the position and dimensions
of which are supplied by the client. Any complex underlying data structure
a client may use when generating the layout is lost in transmission. This
is an intentional limitation.
Additionally, this protocol allows the compositor to deliver arbitrary
user-provided commands associated with a layout to clients. A client
may use these commands to implement runtime configuration/control, or
may ignore them entirely. How the user provides these commands to the
compositor is not specified by this protocol and left to compositor policy.
Warning! The protocol described in this file is currently in the
testing phase. Backward compatible changes may be added together with
the corresponding interface version bump. Backward incompatible changes
can only be done by creating a new major version of the extension.
</description>
<interface name="river_layout_manager_v3" version="2">
<description summary="manage river layout objects">
A global factory for river_layout_v3 objects.
</description>
<request name="destroy" type="destructor">
<description summary="destroy the river_layout_manager object">
This request indicates that the client will not use the
river_layout_manager object any more. Objects that have been created
through this instance are not affected.
</description>
</request>
<request name="get_layout">
<description summary="create a river_layout_v3 object">
This creates a new river_layout_v3 object for the given wl_output.
All layout related communication is done through this interface.
The namespace is used by the compositor to decide which river_layout_v3
object will receive layout demands for the output.
The namespace is required to be be unique per-output. Furthermore,
two separate clients may not share a namespace on separate outputs. If
these conditions are not upheld, the the namespace_in_use event will
be sent directly after creation of the river_layout_v3 object.
</description>
<arg name="id" type="new_id" interface="river_layout_v3"/>
<arg name="output" type="object" interface="wl_output"/>
<arg name="namespace" type="string" summary="namespace of the layout object"/>
</request>
</interface>
<interface name="river_layout_v3" version="2">
<description summary="receive and respond to layout demands">
This interface allows clients to receive layout demands from the
compositor for a specific output and subsequently propose positions and
dimensions of individual views.
</description>
<enum name="error">
<entry name="count_mismatch" value="0" summary="number of
proposed dimensions does not match number of views in layout"/>
<entry name="already_committed" value="1" summary="the layout demand with
the provided serial was already committed"/>
</enum>
<request name="destroy" type="destructor">
<description summary="destroy the river_layout_v3 object">
This request indicates that the client will not use the river_layout_v3
object any more.
</description>
</request>
<event name="namespace_in_use">
<description summary="the requested namespace is already in use">
After this event is sent, all requests aside from the destroy event
will be ignored by the server. If the client wishes to try again with
a different namespace they must create a new river_layout_v3 object.
</description>
</event>
<event name="layout_demand">
<description summary="the compositor requires a layout">
The compositor sends this event to inform the client that it requires a
layout for a set of views.
The usable width and height indicate the space in which the client
can safely position views without interfering with desktop widgets
such as panels.
The serial of this event is used to identify subsequent requests as
belonging to this layout demand. Beware that the client might need
to handle multiple layout demands at the same time.
The server will ignore responses to all but the most recent layout
demand. Thus, clients are only required to respond to the most recent
layout_demand received. If a newer layout_demand is received before
the client has finished responding to an old demand, the client should
abort work on the old demand as any further work would be wasted.
</description>
<arg name="view_count" type="uint" summary="number of views in the layout"/>
<arg name="usable_width" type="uint" summary="width of the usable area"/>
<arg name="usable_height" type="uint" summary="height of the usable area"/>
<arg name="tags" type="uint" summary="tags of the output, 32-bit bitfield"/>
<arg name="serial" type="uint" summary="serial of the layout demand"/>
</event>
<request name="push_view_dimensions">
<description summary="propose dimensions of the next view">
This request proposes a size and position for a view in the layout demand
with matching serial.
A client must send this request for every view that is part of the
layout demand. The number of views in the layout is given by the
view_count argument of the layout_demand event. Pushing too many or
too few view dimensions is a protocol error.
The x and y coordinates are relative to the usable area of the output,
with (0,0) as the top left corner.
</description>
<arg name="x" type="int" summary="x coordinate of view"/>
<arg name="y" type="int" summary="y coordinate of view"/>
<arg name="width" type="uint" summary="width of view"/>
<arg name="height" type="uint" summary="height of view"/>
<arg name="serial" type="uint" summary="serial of layout demand"/>
</request>
<request name="commit">
<description summary="commit a layout">
This request indicates that the client is done pushing dimensions
and the compositor may apply the layout. This completes the layout
demand with matching serial, any other requests sent with the serial
are a protocol error.
The layout_name argument is a user-facing name or short description
of the layout that is being committed. The compositor may for example
display this on a status bar, though what exactly is done with it is
left to the compositor's discretion.
The compositor is free to use this proposed layout however it chooses,
including ignoring it.
</description>
<arg name="layout_name" type="string" summary="name of committed layout"/>
<arg name="serial" type="uint" summary="serial of layout demand"/>
</request>
<event name="user_command">
<description summary="a command sent by the user">
This event informs the client of a command sent to it by the user.
The semantic meaning of the command is left for the client to
decide. It is also free to ignore it entirely if it so chooses.
A layout_demand will be sent after this event if the compositor is
currently using this layout object to arrange the output.
If version 2 or higher of the river_layout_v3 object is bound, the
user_command_tags event is guaranteed to be sent directly before the
user_command event.
</description>
<arg name="command" type="string"/>
</event>
<event name="user_command_tags" since="2">
<description summary="a command sent by the user">
If version 2 or higher of the river_layout_v3 object is bound, this
event will be sent directly before every user_command event. This allows
layout generators to be aware of the active tags when a user command is
sent. This is necessary for generators wanting to keep settings on a
per-tag basis.
</description>
<arg name="tags" type="uint" summary="tags of the output, 32-bit bitfield"/>
</event>
</interface>
</protocol>
0707010000000C000041ED00000000000000000000000265A4F7D200000000000000000000000000000000000000000000001A00000000riverguile-0.1.0+git8/src0707010000000D000081A400000000000000000000000165A4F7D2000002EE000000000000000000000000000000000000002E00000000riverguile-0.1.0+git8/src/call-exit-handler.c#include <libguile.h>
#include <assert.h>
#include "riverguile.h"
static void *call_exit_handler_inner (void *data)
{
assert(data == NULL);
return scm_call_0(context.exit_handler);
}
void *call_exit_handler (void *data)
{
assert(context.exit_handler != NULL);
/* Continuation barrier causes stack unwind on exceptions (i.e. errors
* in the user defined exit handler) to stop here. Otherwise the entire
* stack created by scm_with_guile() would be unwound. This makes
* responding to exceptions nicer.
*/
SCM call_result = scm_c_with_continuation_barrier(
call_exit_handler_inner, NULL
);
if ( call_result == NULL )
return (void *)"ERROR: An exception occured while calling the exit handler.\n";
return NULL;
}
0707010000000E000081A400000000000000000000000165A4F7D20000007D000000000000000000000000000000000000002E00000000riverguile-0.1.0+git8/src/call-exit-handler.h#ifndef RIVERGUILE_CALL_EXIT_HANDLER_H
#define RIVERGUILE_CALL_EXIT_HANDLER_H
void *call_exit_handler (void* data);
#endif
0707010000000F000081A400000000000000000000000165A4F7D2000003C2000000000000000000000000000000000000002E00000000riverguile-0.1.0+git8/src/call-idle-handler.c#include <libguile.h>
#include "seat.h"
#include "call-idle-handler.h"
static void *call_idle_handler_inner (void *data)
{
struct Call_idle_handler_parameters *params =
(struct Call_idle_handler_parameters *)data;
SCM event;
switch (params->event)
{
case IDLE: event = scm_from_utf8_symbol("idle"); break;
case RESUME: event = scm_from_utf8_symbol("resume"); break;
}
return scm_call_1(params->idle->handler, event);
}
void *call_idle_handler (void *data)
{
/* Continuation barrier causes stack unwind on exceptions (i.e. errors
* in the user defined idle handler) to stop here. Otherwise the entire
* stack created by scm_with_guile() would be unwound. This makes
* responding to exceptions nicer.
*/
SCM call_result = scm_c_with_continuation_barrier(
call_idle_handler_inner, data
);
if ( call_result == NULL )
return (void *)"ERROR: An exception occured while calling the idle handler.\n";
return NULL;
}
07070100000010000081A400000000000000000000000165A4F7D20000011C000000000000000000000000000000000000002E00000000riverguile-0.1.0+git8/src/call-idle-handler.h#ifndef RIVERGUILE_CALL_IDLE_HANDLER_H
#define RIVERGUILE_CALL_IDLE_HANDLER_H
#include "seat.h"
enum Idle_handler_event
{
IDLE,
RESUME,
};
struct Call_idle_handler_parameters
{
struct Idle *idle;
enum Idle_handler_event event;
};
void *call_idle_handler (void *data);
#endif
07070100000011000081A400000000000000000000000165A4F7D200000BAC000000000000000000000000000000000000003700000000riverguile-0.1.0+git8/src/call-layout-demand-handler.c#include <assert.h>
#include <libguile.h>
#include "riverguile.h"
#include "output.h"
#include "river-layout-v3.h"
#include "call-layout-demand-handler.h"
static void *call_layout_demand_handler_inner (void *data)
{
struct Call_layout_demand_handler_parameters *params = (struct Call_layout_demand_handler_parameters *)data;
return scm_call_5(
context.layout_demand_handler,
scm_from_uint32(params->view_count),
scm_from_uint32(params->width),
scm_from_uint32(params->height),
scm_from_uint32(params->tags),
scm_from_uint32(params->output->name)
);
}
void *call_layout_demand_handler (void *data)
{
struct Call_layout_demand_handler_parameters *params = (struct Call_layout_demand_handler_parameters *)data;
assert(context.layout_demand_handler != NULL);
assert(scm_is_true(scm_procedure_p(context.layout_demand_handler)) == 1);
/* Continuation barrier causes stack unwind on exceptions (i.e. errors
* in the user defined layout demand handler) to stop here. Otherwise
* the entire stack created by scm_with_guile() would be unwound. This
* makes responding to exceptions nicer.
*/
SCM call_result = scm_c_with_continuation_barrier(
call_layout_demand_handler_inner, data
);
if ( call_result == NULL )
return (void *)"ERROR: An exception occured while calling the layout demand handler.\n";
/* Check integrity of data before firing off any Wayland requests. */
if ( scm_is_false(scm_list_p(call_result)) == 1 )
return (void *)"ERROR: layout-demand-handler did not return a list.\n";
if ( params->view_count != scm_to_uint32(scm_length(call_result)) )
return (void *)"ERROR: Length of list returned by layout-demand-handler does not match view count.\n";
for (uint32_t i = 0; i < params->view_count; i++)
{
SCM elem = scm_list_ref(call_result, scm_from_uint32(i));
if ( scm_is_false(scm_list_p(elem)) == 1 )
return (void *)"ERROR: View dimensions list is not a list.\n";
if ( scm_to_uint32(scm_length(elem)) != 4 )
return (void *)"ERROR: View dimensions list length does not equal four (x, y, width, height).\n";
for (uint8_t j = 0; j < 4; j++)
{
SCM list_elem = scm_list_ref(elem, scm_from_int(j));
if ( scm_is_false(scm_number_p(list_elem)) == 1 )
return (void *)"ERROR: Encountered non-numerical view dimensions.\n";
}
}
for (uint32_t i = 0; i < params->view_count; i++)
{
SCM elem = scm_list_ref(call_result, scm_from_uint32(i));
uint32_t x = scm_to_uint32(scm_inexact_to_exact(
scm_round_number(scm_list_ref(elem, scm_from_int(0)))));
uint32_t y = scm_to_uint32(scm_inexact_to_exact(
scm_round_number(scm_list_ref(elem, scm_from_int(1)))));
uint32_t w = scm_to_uint32(scm_inexact_to_exact(
scm_round_number(scm_list_ref(elem, scm_from_int(2)))));
uint32_t h = scm_to_uint32(scm_inexact_to_exact(
scm_round_number(scm_list_ref(elem, scm_from_int(3)))));
river_layout_v3_push_view_dimensions(
params->output->layout,
x, y, w, h,
params->serial
);
}
return NULL;
}
07070100000012000081A400000000000000000000000165A4F7D20000012D000000000000000000000000000000000000003700000000riverguile-0.1.0+git8/src/call-layout-demand-handler.h#ifndef RIVERGUILE_CALL_LAYOUT_DEMAND_HANDLER_H
#define RIVERGUILE_CALL_LAYOUT_DEMAND_HANDLER_H
#include <libguile.h>
struct Call_layout_demand_handler_parameters
{
uint32_t view_count, width, height, serial, tags;
struct Output *output;
};
void *call_layout_demand_handler (void *data);
#endif
07070100000013000081A400000000000000000000000165A4F7D20000046B000000000000000000000000000000000000003600000000riverguile-0.1.0+git8/src/call-user-command-handler.c#include <assert.h>
#include <libguile.h>
#include "riverguile.h"
#include "output.h"
#include "call-user-command-handler.h"
static void *call_user_command_handler_inner (void *data)
{
struct Call_user_command_parameters *params = (struct Call_user_command_parameters *)data;
return scm_call_3(
context.user_command_handler,
scm_from_utf8_string(params->cmd),
scm_from_uint32(params->output->user_command_tags),
scm_from_uint32(params->output->name)
);
}
void *call_user_command_handler (void *data)
{
assert(context.user_command_handler != NULL);
assert(scm_is_true(scm_procedure_p(context.user_command_handler)) == 1);
/* Continuation barrier causes stack unwind on exceptions (i.e. errors
* in the user defined user-command handler) to stop here. Otherwise
* the entire stack created by scm_with_guile() would be unwound. This
* makes responding to exceptions nicer.
*/
SCM call_result = scm_c_with_continuation_barrier(
call_user_command_handler_inner, data
);
if ( call_result == NULL )
return (void *)"ERROR: An exception occured while calling the user-command handler.\n";
return NULL;
}
07070100000014000081A400000000000000000000000165A4F7D2000000FE000000000000000000000000000000000000003600000000riverguile-0.1.0+git8/src/call-user-command-handler.h#ifndef RIVERGUILE_CALL_USER_COMMAND_HANDLER_H
#define RIVERGUILE_CALL_USER_COMMAND_HANDLER_H
#include "output.h"
struct Call_user_command_parameters
{
struct Output *output;
const char *cmd;
};
void *call_user_command_handler (void *data);
#endif
07070100000015000081A400000000000000000000000165A4F7D20000208B000000000000000000000000000000000000002800000000riverguile-0.1.0+git8/src/load-script.c#include <assert.h>
#include <stdio.h>
#include <stdint.h>
#include <libguile.h>
#include <string.h>
#include "riverguile.h"
#include "output.h"
#include "seat.h"
#include "river-control-unstable-v1.h"
/**
* ISO C forbids casting a function pointer to a void pointer because on some
* architectures they have different sizes. However scm_c_define_gsubr() wants
* a function pointer as a void pointer, which trips -Wpedantic. Compiling C
* without pedantic errors is not a reasonable option in my opinion, so instead
* we'll have to resort to this hack.
*/
#define scm_c_define_gsubr_fix(NAME, REQ, OPT, RST, FN) \
{ const long int ptr = (long int)FN; scm_c_define_gsubr(NAME, REQ, OPT, RST, (void *)ptr); }
static uint32_t extract_ms_from_idle_key (SCM key)
{
SCM key_split = scm_string_split(
scm_symbol_to_string(key),
scm_to_char_set(scm_from_utf8_string(":"))
);
if ( scm_to_uint32(scm_length(key_split)) != 2 )
goto error;
SCM maybe_number = scm_string_to_number(scm_cadr(key_split), scm_from_int(10));
if ( scm_is_false(maybe_number) == 1 )
goto error;
int32_t ms = scm_to_int32(maybe_number);
if ( ms < 0 )
goto error;
return (uint32_t)ms * 1000;
error:
scm_error_scm(
scm_from_utf8_symbol("wrong-type-arg"),
scm_from_utf8_string("install-handler"),
scm_from_utf8_string("First argument: Excpected 'idle:<positive integer>."),
SCM_BOOL_F,
scm_list_1(key)
);
return 0;
}
static SCM install_handler (SCM key, SCM proc)
{
if ( scm_is_false(scm_symbol_p(key)) == 1 )
{
scm_error_scm(
scm_from_utf8_symbol("wrong-type-arg"),
scm_from_utf8_string("install-handler"),
scm_from_utf8_string("First argument must be a symbol."),
SCM_BOOL_F,
scm_list_1(key)
);
return SCM_UNSPECIFIED;
}
// TODO check if the procedure has the right amount of arguments.
if ( scm_is_false(scm_procedure_p(proc)) == 1 )
{
scm_error_scm(
scm_from_utf8_symbol("wrong-type-arg"),
scm_from_utf8_string("install-handler"),
scm_from_utf8_string("Second argument must be a procedure."),
SCM_BOOL_F,
scm_list_1(proc)
);
return SCM_UNSPECIFIED;
}
if ( scm_is_eq(scm_from_utf8_symbol("layout-demand"), key) == 1 )
{
if ( context.layout_manager == NULL )
{
fputs("ERROR: Trying to install layout-demand handler but server does not support river-layout-v3.\n", stderr);
fputs("INFO: This error is not fatal, but means riverguile will not provide any layout.\n", stderr);
return SCM_BOOL_F;
}
context.mode = CONTINOUS;
context.layout_demand_handler = proc;
/* Configure all outputs to expose layouts. */
struct Output *output;
wl_list_for_each(output, &context.outputs, link)
output_configure_layout(output);
}
else if ( scm_is_eq(scm_from_utf8_symbol("user-command"), key) == 1)
{
/* No need to check if the interface exists since it's only
* used when a layout-demand handler is configured.
*/
context.user_command_handler = proc;
}
else if ( scm_is_eq(scm_from_utf8_symbol("exit"), key) == 1)
context.exit_handler = proc;
else if ( scm_is_true(scm_string_prefix_p(scm_from_utf8_string("idle:"), scm_symbol_to_string(key),
scm_from_int(0), scm_from_int(5),
scm_from_int(0), scm_string_length(scm_symbol_to_string(key)))) == 1 )
{
if ( context.idle_notifier == NULL )
{
fputs("ERROR: Trying to install idle handler but server does not support ext-idle-notify-v1.\n", stderr);
fputs("INFO: This error is not fatal, but means riverguile will not be able to call any idle handler.\n", stderr);
return SCM_BOOL_F;
}
if ( wl_list_length(&context.seats) == 0 )
{
fputs("ERROR: Trying to install idle handler but server did not advertise any seats.\n", stderr);
fputs("INFO: This error is not fatal, but means riverguile will not be able to call any idle handler.\n", stderr);
return SCM_BOOL_F;
}
context.mode = CONTINOUS;
/* Just use the first seat. River only supports a single one anyway. */
struct Seat *seat;
wl_list_for_each(seat, &context.seats, link)
break;
uint32_t ms = extract_ms_from_idle_key(key);
if (!seat_add_idle(seat, proc, ms))
{
scm_error_scm(
scm_from_utf8_symbol("memory-allocation-error"),
scm_from_utf8_string("install-handler"),
SCM_BOOL_F,
SCM_BOOL_F,
SCM_BOOL_F
);
return SCM_UNSPECIFIED;
}
}
else
{
scm_error_scm(
// TODO should this be 'misc-error instead?
scm_from_utf8_symbol("out-of-range"),
scm_from_utf8_string("install-handler"),
scm_from_utf8_string("Unknown key: ~A"),
scm_list_1(key),
scm_list_1(key)
);
return SCM_UNSPECIFIED;
}
return SCM_BOOL_T;
}
static SCM riverctl (SCM first, SCM rest)
{
if ( context.river_control == NULL )
{
fputs("ERROR: User script attempts to send river command but river-control-unstable-v1 not available.\n", stderr);
fputs("INFO: This error is not fatal, however riverguile will not be able to send any commands to river.\n", stderr);
return SCM_BOOL_F;
}
if ( wl_list_length(&context.seats) == 0 )
{
fputs("ERROR: User script attempts to send river command but server did not advertise any seats.\n", stderr);
fputs("INFO: This error is not fatal, however riverguile will not be able to send any commands to river.\n", stderr);
return SCM_BOOL_F;
}
if ( scm_is_string(first) != 1 )
goto error;
assert(scm_is_true(scm_list_p(rest)) == 1);
const uint32_t rest_len = scm_to_uint32(scm_length(rest));
for (uint32_t i = 0; i < rest_len; i++)
if ( scm_is_string(scm_list_ref(rest, scm_from_uint32(i))) != 1 )
goto error;
char *first_owned = scm_to_utf8_stringn(first, 0);
zriver_control_v1_add_argument(context.river_control, first_owned);
free(first_owned);
for (uint32_t i = 0; i < rest_len; i++)
{
char *owned = scm_to_utf8_stringn(scm_list_ref(rest, scm_from_uint32(i)), 0);
zriver_control_v1_add_argument(context.river_control, owned);
free(owned);
}
/* Just use the first seat. River only supports a single one anyway. */
struct Seat *seat;
wl_list_for_each(seat, &context.seats, link)
break;
/* While river does tell us about the status of the command, I do not
* want to make use of that in riverguile for multiple reasons.
* For one, the reporting is of course async, meaning we could not raise
* a guile error in response to failed commands, even if we wanted to.
* Riverguile could allow to install a handler for the callback, however
* I do not sett the use. There are two riverctl commands that return
* useful data as a string, however using that for scripting would be
* very hacky and I prefer dedicated well designed interfaces. So we
* just destroy the callback before it even fires.
*/
zriver_command_callback_v1_destroy(
zriver_control_v1_run_command(context.river_control, seat->wl_seat)
);
return SCM_BOOL_T;
error:
scm_error_scm(
scm_from_utf8_symbol("wrong-type-arg"),
scm_from_utf8_string("riverctl"),
scm_from_utf8_string("All arguments must be strings."),
SCM_BOOL_F,
SCM_BOOL_F
);
return SCM_UNSPECIFIED;
}
static void *load_script_inner (void *data)
{
const char *path = (char *)data;
/* scm_primitive_load_path() searches guiles load-path when encountering
* a relative path. That should never happen here though.
*/
assert(path[0] == '/');
return scm_primitive_load_path(scm_from_utf8_string(path));
}
void *load_script (void *data)
{
/* Note: All guile objects are garbage collected. */
scm_c_define_gsubr_fix("install-handler", 2, 0, 0, install_handler);
scm_c_define_gsubr_fix("riverctl", 1, 0, 1, riverctl);
/* Continuation barrier causes stack unwind on exceptions to stop here.
* Otherwise the entire stack created by scm_with_guile() would be
* unwound. This makes responding to exceptions nicer.
*/
SCM call_result = scm_c_with_continuation_barrier(
load_script_inner, data
);
if ( call_result == NULL )
return (void *)"ERROR: Fatal error while loading layout script.\n";
/* Checked in the installer functions. */
if ( context.layout_demand_handler != NULL )
assert(scm_is_true(scm_procedure_p(context.layout_demand_handler)) == 1);
if ( context.user_command_handler != NULL )
assert(scm_is_true(scm_procedure_p(context.user_command_handler)) == 1);
if ( context.exit_handler != NULL )
assert(scm_is_true(scm_procedure_p(context.exit_handler)) == 1);
return NULL;
}
07070100000016000081A400000000000000000000000165A4F7D20000007D000000000000000000000000000000000000002800000000riverguile-0.1.0+git8/src/load-script.h#ifndef RIVERGUILE_LOAD_SCRIPT_H_INCLUDED
#define RIVERGUILE_LOAD_SCRIPT_H_INCLUDED
void *load_script (void *data);
#endif
07070100000017000081A400000000000000000000000165A4F7D200000D55000000000000000000000000000000000000002300000000riverguile-0.1.0+git8/src/output.c#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <errno.h>
#include <libguile.h>
#include <assert.h>
#include "river-layout-v3.h"
#include "riverguile.h"
#include "output.h"
#include "call-layout-demand-handler.h"
#include "call-user-command-handler.h"
static void layout_handle_layout_demand (void *data, struct river_layout_v3 *river_layout_v3,
uint32_t view_count, uint32_t width, uint32_t height, uint32_t tags, uint32_t serial)
{
struct Output *output = (struct Output *)data;
struct Call_layout_demand_handler_parameters params = {
.view_count = view_count,
.width = width,
.height = height,
.serial = serial,
.tags = tags,
.output = output,
};
void *res = scm_with_guile(call_layout_demand_handler, (void *)¶ms);
if ( res != NULL )
{
fputs(res, stderr);
fputs("INFO: This error is not fatal.\n", stderr);
return;
}
// TODO allow setting layout name from user installed layout demand handler
river_layout_v3_commit(output->layout, "(🐦)", serial);
}
static void layout_handle_user_command (void *data,
struct river_layout_v3 *river_layout, const char *command)
{
if ( context.user_command_handler == NULL )
return;
struct Output *output = (struct Output *)data;
struct Call_user_command_parameters params = {
.cmd = command,
.output = output,
};
void *res = scm_with_guile(call_user_command_handler, (void *)¶ms);
if ( res != NULL )
{
fputs(res, stderr);
fputs("INFO: This error is not fatal.\n", stderr);
}
}
static void layout_handle_user_command_tags (void *data,
struct river_layout_v3 *river_layout, uint32_t tags)
{
struct Output *output = (struct Output *)data;
output->user_command_tags = tags;
}
static void layout_handle_namespace_in_use (void *data, struct river_layout_v3 *river_layout_v3)
{
fputs("ERROR: Namespace already in use.\n", stderr);
context.ret = EXIT_FAILURE;
context.loop = false;
}
static const struct river_layout_v3_listener layout_listener = {
.namespace_in_use = layout_handle_namespace_in_use,
.layout_demand = layout_handle_layout_demand,
.user_command = layout_handle_user_command,
.user_command_tags = layout_handle_user_command_tags,
};
void output_configure_layout (struct Output *output)
{
assert(context.layout_manager != NULL);
assert(context.layout_demand_handler != NULL);
if ( output->layout != NULL )
return;
output->layout = river_layout_manager_v3_get_layout(
context.layout_manager, output->wl_output, "riverguile"
);
river_layout_v3_add_listener(output->layout, &layout_listener, output);
}
struct Output *output_create (struct wl_output *wl_output, uint32_t name)
{
struct Output *output = calloc(1, sizeof(struct Output));
if ( output == NULL )
{
fprintf(stderr, "ERROR: calloc: %s\n", strerror(errno));
return NULL;
}
output->name = name;
output->wl_output = wl_output;
/* Only bind layout if we need it. Outputs advertised in the initial
* registry burst, before the script is loaded, will always skip this,
* however it is necessary for outputs added later.
*/
if ( context.layout_manager != NULL && context.layout_demand_handler != NULL )
output_configure_layout(output);
return output;
}
void output_destroy (struct Output *output)
{
if ( output->layout != NULL )
river_layout_v3_destroy(output->layout);
assert(output->wl_output != NULL);
wl_output_destroy(output->wl_output);
free(output);
}
07070100000018000081A400000000000000000000000165A4F7D2000002D2000000000000000000000000000000000000002300000000riverguile-0.1.0+git8/src/output.h#ifndef RIVERGUILE_OUTPUT_H
#define RIVERGUILE_OUTPUT_H
#include <stdbool.h>
#include <wayland-client.h>
#include "river-layout-v3.h"
struct Output
{
struct wl_list link;
struct wl_output *wl_output;
struct river_layout_v3 *layout;
uint32_t name;
/* Tags for the next user command. Due to backwards compatability, the
* layout protocol sends us the currently active tags for a user command
* in a separate event before the actual user command. This event is
* guaranteed to be received.
*/
uint32_t user_command_tags;
};
struct Output *output_create (struct wl_output *wl_output, uint32_t name);
void output_destroy (struct Output *output);
void output_configure_layout (struct Output *output);
#endif
07070100000019000081A400000000000000000000000165A4F7D2000029C9000000000000000000000000000000000000002700000000riverguile-0.1.0+git8/src/riverguile.c#include <ctype.h>
#include <signal.h>
#include <stdbool.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <errno.h>
#include <assert.h>
#include <setjmp.h>
#include <wayland-client.h>
#include <libguile.h>
#ifdef __linux__
#include <features.h>
#ifdef __GLIBC__
#include<execinfo.h>
#endif
#endif
#include "river-layout-v3.h"
#include "ext-idle-notify-v1.h"
#include "river-control-unstable-v1.h"
#include "load-script.h"
#include "call-exit-handler.h"
#include "riverguile.h"
#include "output.h"
#include "seat.h"
struct Context context = {
/* Handlers are initially NULL instead of SCM_EOL because I am not sure whether
* scm_null_p() is safe to use outside of a guile context and if yes, whether
* that is intended or will disappear in the future. Special care must be taken
* to never call any scm_* function on these while they are NULL.
*/
.layout_demand_handler = NULL,
.user_command_handler = NULL,
.exit_handler = NULL,
.loop = true,
.ret = EXIT_SUCCESS,
};
jmp_buf skip_main_loop;
static void registry_handle_global (void *data, struct wl_registry *registry,
uint32_t name, const char *interface, uint32_t version)
{
if ( strcmp(interface, river_layout_manager_v3_interface.name) == 0 )
{
context.layout_manager = wl_registry_bind(
registry, name, &river_layout_manager_v3_interface, 2
);
}
else if ( strcmp(interface, zriver_control_v1_interface.name) == 0 )
{
context.river_control = wl_registry_bind(
registry, name, &zriver_control_v1_interface, 1
);
}
else if ( strcmp(interface, ext_idle_notifier_v1_interface.name) == 0 )
{
context.idle_notifier = wl_registry_bind(
registry, name, &ext_idle_notifier_v1_interface, 1
);
}
else if ( strcmp(interface, wl_output_interface.name) == 0 )
{
struct wl_output *wl_output = wl_registry_bind(
registry, name, &wl_output_interface, 1
);
struct Output *output = output_create(wl_output, name);
if ( output == NULL )
{
wl_output_destroy(wl_output);
context.ret = EXIT_FAILURE;
context.loop = false;
return;
}
wl_list_insert(&context.outputs, &output->link);
}
else if ( strcmp(interface, wl_seat_interface.name) == 0 )
{
struct wl_seat *wl_seat = wl_registry_bind(
registry, name, &wl_seat_interface, 1
);
struct Seat *seat = seat_create(wl_seat, name);
if ( seat == NULL )
{
wl_seat_destroy(wl_seat);
context.ret = EXIT_FAILURE;
context.loop = false;
return;
}
wl_list_insert(&context.seats, &seat->link);
}
}
static void registry_handle_global_remove (void *data, struct wl_registry *registry,
uint32_t name)
{
struct Output *output, *tmp_o;
wl_list_for_each_safe(output, tmp_o, &context.outputs, link)
{
if ( output->name != name )
continue;
wl_list_remove(&output->link);
output_destroy(output);
return;
}
struct Seat *seat, *tmp_s;
wl_list_for_each_safe(seat, tmp_s, &context.seats, link)
{
if ( seat->name != name )
continue;
wl_list_remove(&seat->link);
seat_destroy(seat);
return;
}
}
static const struct wl_registry_listener registry_listener = {
.global = registry_handle_global,
.global_remove = registry_handle_global_remove,
};
static void sync_handle_done (void *, struct wl_callback *, uint32_t);
static const struct wl_callback_listener sync_callback_listener = {
.done = sync_handle_done,
};
static void sync_handle_done (void *data, struct wl_callback *wl_callback, uint32_t other_data)
{
static int i = 0;
if ( i == 1 )
{
assert(context.mode == ONESHOT);
context.loop = false;
return;
}
wl_callback_destroy(wl_callback);
context.sync_callback = NULL;
/* Load the script after connecting to the server and binding interfaces
* to allow calling Wayland requests from it.
*/
assert(context.path != NULL);
void *res = scm_with_guile(load_script, (void *)context.path);
if ( res != NULL )
{
fputs((char *)res, stderr);
context.ret = EXIT_FAILURE;
context.loop = false;
return;
}
if ( context.layout_demand_handler == NULL
&& context.user_command_handler != NULL )
{
fputs("ERROR: Installing user-command handler without installing a layout-demand handler is not allowed.\n", stderr);
fputs("INFO: This error is not fatal, but means riverguile will not provide any layout.\n", stderr);
}
switch (context.mode)
{
case ONESHOT:
/* Oneshot mode. Sync again so we are sure that all commands
* have been send, then exit.
*/
assert(i == 0);
i++;
context.sync_callback = wl_display_sync(context.wl_display);
wl_callback_add_listener(context.sync_callback, &sync_callback_listener, NULL);
fputs("INFO: No handlers installed: Riverguile will exit.\n", stderr);
break;
case CONTINOUS:
fputs("INFO: At least one handler installed: Riverguile will run continously.\n", stderr);
break;
}
}
static void handle_interrupt (int signum)
{
fputs("INFO: Killed 💀\n", stderr);
context.loop = false;
longjmp(skip_main_loop, 1);
}
/**
* Intercept error signals (like SIGSEGV and SIGFPE) so that we can try to
* print a fancy error message and a backtracke before letting the system kill us.
*/
static void handle_error (int signum)
{
const char *msg =
"\n"
"┌──────────────────────────────────────────┐\n"
"│ │\n"
"│ riverguile has crashed. │\n"
"│ │\n"
"│ This is most likely a bug, so please │\n"
"│ report this to the mailing list. │\n"
"│ │\n"
"│ ~leon_plickat/public-inbox@lists.sr.ht │\n"
"│ │\n"
"└──────────────────────────────────────────┘\n"
"\n";
fputs(msg, stderr);
/* Set up the default handlers to deal with the rest. We do this before
* attempting to get a backtrace, because sometimes that could also
* cause a SEGFAULT and we don't want a funny signal loop to happen.
*/
signal(signum, SIG_DFL);
#ifdef __linux__
#ifdef __GLIBC__
fputs("Attempting to get backtrace:\n", stderr);
void *buffer[255];
const int calls = backtrace(buffer, sizeof(buffer) / sizeof(void *));
backtrace_symbols_fd(buffer, calls, fileno(stderr));
fputs("\n", stderr);
#endif
#endif
/* Easiest way of calling the default signal handler. */
kill(getpid(), signum);
}
static char *formatted_buffer (const char *fmt, ...)
{
/* Determine length of formatted text. */
va_list args;
va_start(args, fmt);
/* +1 for NULL. */
unsigned long len = (unsigned long)vsnprintf(NULL, 0, fmt, args) + 1;
va_end(args);
char *buffer = calloc(1, len);
if ( buffer == NULL )
{
fprintf(stderr, "ERROR: calloc: %s\n", strerror(errno));
return NULL;
}
/* Finally write formatted text into buffer. */
va_start(args, fmt);
vsnprintf(buffer, len, fmt, args);
va_end(args);
return buffer;
}
static char *get_script_path (char *relative_path)
{
assert(relative_path != NULL);
char *path = NULL;
if ( relative_path[0] == '/' )
path = formatted_buffer("%s", relative_path);
else
{
/* When scm_primitive_load_path() receives a relative path, it
* tries to look it up in the guile module path. So we must
* always provide it an absolute path.
*/
char buffer[4 * 1024];
char *cwd = getcwd(buffer, 4 * 1024);
if ( cwd == NULL )
{
fprintf(stderr, "ERROR: getcwd: %s\n", strerror(errno));
return NULL;
}
path = formatted_buffer("%s/%s", cwd, relative_path);
}
if ( path == NULL )
return NULL;
if ( access(path, R_OK) != 0 )
{
fprintf(stderr, "ERROR: Script '%s' is not readable.\n", path);
free(path);
return NULL;
}
return path;
}
int main (int argc, char *argv[])
{
if ( argc != 2
|| strcmp(argv[1], "--help") == 0
|| strcmp(argv[1], "-h") == 0
|| strcmp(argv[1], "-?") == 0 )
{
fprintf(stderr, "USAGE: %s path-to-script\n", argv[0]);
return EXIT_FAILURE;
}
fputs("INFO: Welcome to riverguile!\n", stderr);
signal(SIGSEGV, handle_error);
signal(SIGFPE, handle_error);
signal(SIGINT, handle_interrupt);
context.path = get_script_path(argv[1]);
if ( context.path == NULL )
{
context.ret = EXIT_FAILURE;
goto early_exit;
}
fprintf(stderr, "INFO: Using script: %s\n", context.path);
wl_list_init(&context.outputs);
wl_list_init(&context.seats);
/* We query the display name here instead of letting wl_display_connect()
* figure it out itself, because libwayland (for legacy reasons) falls
* back to using "wayland-0" when $WAYLAND_DISPLAY is not set, which is
* generally not desirable.
*/
const char *display_name = getenv("WAYLAND_DISPLAY");
if ( display_name == NULL )
{
fputs("ERROR: WAYLAND_DISPLAY is not set.\n", stderr);
context.ret = EXIT_FAILURE;
goto early_exit;
}
context.wl_display = wl_display_connect(display_name);
if ( context.wl_display == NULL )
{
fputs("ERROR: Can not connect to wayland display.\n", stderr);
context.ret = EXIT_FAILURE;
goto early_exit;
}
context.wl_registry = wl_display_get_registry(context.wl_display);
wl_registry_add_listener(context.wl_registry, ®istry_listener, NULL);
context.sync_callback = wl_display_sync(context.wl_display);
wl_callback_add_listener(context.sync_callback, &sync_callback_listener, NULL);
if ( setjmp(skip_main_loop) == 0 )
while ( context.loop && wl_display_dispatch(context.wl_display) > 0 );
if ( context.exit_handler != NULL )
{
void *res = scm_with_guile(call_exit_handler, NULL);
if ( res != NULL )
{
fputs((char *)res, stderr);
context.ret = EXIT_FAILURE;
context.loop = false;
}
}
struct Output *output, *tmp_o;
wl_list_for_each_safe(output, tmp_o, &context.outputs, link)
{
wl_list_remove(&output->link);
output_destroy(output);
}
struct Seat *seat, *tmp_s;
wl_list_for_each_safe(seat, tmp_s, &context.seats, link)
{
wl_list_remove(&seat->link);
seat_destroy(seat);
}
if ( context.idle_notifier != NULL )
ext_idle_notifier_v1_destroy(context.idle_notifier);
if ( context.layout_manager != NULL )
river_layout_manager_v3_destroy(context.layout_manager);
if ( context.river_control != NULL )
zriver_control_v1_destroy(context.river_control);
if ( context.sync_callback != NULL )
wl_callback_destroy(context.sync_callback);
if ( context.wl_registry != NULL )
wl_registry_destroy(context.wl_registry);
wl_display_disconnect(context.wl_display);
early_exit:
if ( context.path != NULL )
free(context.path);
fputs("INFO: Exiting.\n", stderr);
return context.ret;
}
0707010000001A000081A400000000000000000000000165A4F7D2000003C3000000000000000000000000000000000000002700000000riverguile-0.1.0+git8/src/riverguile.h#ifndef RIVERGUILE_RIVERGUILE_H
#define RIVERGUILE_RIVERGUILE_H
#include <stdbool.h>
#include <wayland-client.h>
#include <libguile.h>
#include "seat.h"
enum Riverguile_mode
{
/* Riverguile is used only for configuring river and will exit after
* the init script has been loaded.
*/
ONESHOT = 0,
/* Riverguile need to run continous, because we have handlers installed
* f.e. for layouts or idle.
*/
CONTINOUS,
};
struct Context
{
SCM layout_demand_handler;
SCM user_command_handler;
SCM exit_handler;
enum Riverguile_mode mode;
bool loop;
int ret;
struct wl_display *wl_display;
struct wl_registry *wl_registry;
struct wl_callback *sync_callback;
struct river_layout_manager_v3 *layout_manager;
struct ext_idle_notifier_v1 *idle_notifier;
struct zriver_control_v1 *river_control;
struct wl_list seats;
struct wl_list outputs;
char *path;
};
extern struct Context context;
#endif
0707010000001B000081A400000000000000000000000165A4F7D200000ACE000000000000000000000000000000000000002100000000riverguile-0.1.0+git8/src/seat.c#include <stdio.h>
#include <stdlib.h>
#include <stdbool.h>
#include <string.h>
#include <errno.h>
#include <assert.h>
#include "ext-idle-notify-v1.h"
#include "riverguile.h"
#include "seat.h"
#include "call-idle-handler.h"
static void idle_notification_handle_idled (void *data,
struct ext_idle_notification_v1 *ext_idle_notification_v1)
{
struct Idle *idle = (struct Idle *)data;
assert(idle->handler != NULL);
struct Call_idle_handler_parameters params = {
.idle = idle,
.event = IDLE,
};
void *res = scm_with_guile(call_idle_handler, ¶ms);
if ( res != NULL )
fputs((char *)res, stderr);
}
static void idle_notification_handle_resumed (void *data,
struct ext_idle_notification_v1 *ext_idle_notification_v1)
{
struct Idle *idle = (struct Idle *)data;
assert(idle->handler != NULL);
struct Call_idle_handler_parameters params = {
.idle = idle,
.event = RESUME,
};
void *res = scm_with_guile(call_idle_handler, ¶ms);
if ( res != NULL )
fputs((char *)res, stderr);
}
static const struct ext_idle_notification_v1_listener idle_notification_listener = {
.idled = idle_notification_handle_idled,
.resumed = idle_notification_handle_resumed,
};
bool seat_add_idle (struct Seat *seat, SCM proc, uint32_t ms)
{
assert(context.idle_notifier != NULL);
struct Idle *idle = calloc(1, sizeof(struct Idle));
if ( idle == NULL )
return false;
idle->ms = ms;
idle->seat = seat;
idle->handler = proc;
idle->idle_notification = ext_idle_notifier_v1_get_idle_notification(
context.idle_notifier,
idle->ms,
seat->wl_seat
);
ext_idle_notification_v1_add_listener(
idle->idle_notification,
&idle_notification_listener,
idle
);
wl_list_insert(&seat->idles, &idle->link);
return true;
}
static void idle_destroy (struct Idle *idle)
{
// TODO XXX how do we tell guile it is allowed to clean up the handler?
// maybe by entering guile mode one more time at exit?
// we could also define an 'exit handler
if ( idle->idle_notification != NULL )
{
assert(idle->seat != NULL);
ext_idle_notification_v1_destroy(idle->idle_notification);
}
else
{
assert(idle->seat == NULL);
}
free(idle);
}
struct Seat *seat_create (struct wl_seat *wl_seat, uint32_t name)
{
struct Seat *seat = calloc(1, sizeof(struct Seat));
if ( seat == NULL )
{
fprintf(stderr, "ERROR: calloc: %s\n", strerror(errno));
return NULL;
}
seat->name = name;
seat->wl_seat = wl_seat;
wl_list_init(&seat->idles);
return seat;
}
void seat_destroy (struct Seat *seat)
{
struct Idle *idle, *tmp_i;
wl_list_for_each_safe(idle, tmp_i, &seat->idles, link)
{
wl_list_remove(&idle->link);
idle_destroy(idle);
}
assert(seat->wl_seat != NULL);
wl_seat_destroy(seat->wl_seat);
free(seat);
}
0707010000001C000081A400000000000000000000000165A4F7D200000225000000000000000000000000000000000000002100000000riverguile-0.1.0+git8/src/seat.h#ifndef RIVERGUILE_SEAT_H
#define RIVERGUILE_SEAT_H
#include <stdbool.h>
#include <wayland-client.h>
#include <libguile.h>
struct Seat
{
struct wl_list link;
struct wl_seat *wl_seat;
uint32_t name;
struct wl_list idles;
};
struct Idle
{
struct Seat *seat;
struct wl_list link;
struct ext_idle_notification_v1 *idle_notification;
SCM handler;
uint32_t ms;
};
struct Seat *seat_create (struct wl_seat *wl_seat, uint32_t name);
void seat_destroy (struct Seat *seat);
bool seat_add_idle (struct Seat *seat, SCM proc, uint32_t ms);
#endif
07070100000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000B00000000TRAILER!!!211 blocks
