koma/i3
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Replace http:// with https:// where applicable

Browse Source 
The testcases will be updated automatically in a separate commit.
This commit is contained in:
Michael Stapelberg
2017-09-24 10:19:07 +02:00
parent eadc9a8461
commit aa0b1f599f
50 changed files with 108 additions and 108 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/asciidoc-git.conf
View File

@ -520,8 +520,8 @@ cellspacing="0" cellpadding="4">
[header]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="{lang=en}">
"https://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="https://www.w3.org/1999/xhtml" xml:lang="{lang=en}">
<head>
<link rel="icon" type="image/png" href="/favicon.png">
<meta http-equiv="Content-Type" content="{quirks=application/xhtml+xml}{quirks?text/html}; charset={encoding}" />
@ -647,7 +647,7 @@ endif::doctype-manpage[]
</div>
{disable-javascript%<div id="footnotes"><hr /></div>}
<div id="footer" lang="de">
© 2009 Michael Stapelberg, <a href="http://i3wm.org/impress.html">Impressum</a>
© 2009 Michael Stapelberg, <a href="https://i3wm.org/impress.html">Impressum</a>
</div>
</body>
</html>

16
docs/debugging
View File

@ -32,8 +32,8 @@ if you can.
4.7-85-g9c15b95 (development version)::
Your version is 85 commits newer than 4.7, and the git revision of your
version is +9c15b95+. Go to http://code.i3wm.org/i3/commit/?h=next and see if
the line "commit" starts with the same revision. If so, you are using the
version is +9c15b95+. Go to https://github.com/i3/i3/commits/next and see if
the most recent commit starts with the same revision. If so, you are using the
latest version.
Development versions of i3 have logging enabled by default and are compiled
@ -109,9 +109,9 @@ No matter whether i3 misbehaved in some way without crashing or whether it just
crashed, the logfile provides all information necessary to debug the problem.
To upload a compressed version of the logfile (for a bugreport), use:
------------------------------------------------------------------------------
DISPLAY=:0 i3-dump-log | bzip2 -c | curl --data-binary @- http://logs.i3wm.org
------------------------------------------------------------------------------
-------------------------------------------------------------------------------
DISPLAY=:0 i3-dump-log | bzip2 -c | curl --data-binary @- https://logs.i3wm.org
-------------------------------------------------------------------------------
This command does not depend on i3 (it also works while i3 displays
the crash dialog), but it requires a working X11 connection.
@ -154,9 +154,9 @@ you found the section which clearly highlights the problem, additional
information might be necessary to completely diagnose the problem.
When debugging with us in IRC, be prepared to use a so called nopaste service
such as http://nopaste.info or http://pastebin.com because pasting large
amounts of text in IRC sometimes leads to incomplete lines (servers have line
length limitations) or flood kicks.
such as https://pastebin.com because pasting large amounts of text in IRC
sometimes leads to incomplete lines (servers have line length limitations) or
flood kicks.
== Debugging i3bar

6
docs/hacking-howto
View File

@ -52,8 +52,8 @@ Here’s a memory refresher:
== Using git / sending patches
For a short introduction into using git, see
http://web.archive.org/web/20121024222556/http://www.spheredev.org/wiki/Git_for_the_lazy
or, for more documentation, see http://git-scm.com/documentation
https://web.archive.org/web/20121024222556/http://www.spheredev.org/wiki/Git_for_the_lazy
or, for more documentation, see https://git-scm.com/documentation
Please talk to us before working on new features to see whether they will be
accepted. A good way for this is to open an issue and asking for opinions on it.
@ -156,7 +156,7 @@ workspace, the split container we are talking about is the workspace.
To get an impression of how different layouts are represented, just play around
and look at the data structures -- they are exposed as a JSON hash. See
http://i3wm.org/docs/ipc.html#_tree_reply for documentation on that and an
https://i3wm.org/docs/ipc.html#_tree_reply for documentation on that and an
example.
== Files

6
docs/i3-pod2html
View File

@ -31,7 +31,7 @@ $parser->html_header_before_title(
<meta charset="utf-8">
<meta name="generator" content="Pod::Simple::HTML">
<meta name="description" content="i3 Perl documentation">
<link rel="stylesheet" href="http://i3wm.org/css/style.css" type="text/css" />
<link rel="stylesheet" href="https://i3wm.org/css/style.css" type="text/css" />
<style type="text/css">
.pod pre {
background: #333;
@ -75,9 +75,9 @@ $parser->html_header_after_title(
<ul id="nav">
<li><a style="border-bottom: 2px solid #fff" href="/docs">Docs</a></li>
<li><a href="/screenshots">Screens</a></li>
<li><a href="http://faq.i3wm.org/">FAQ</a></li>
<li><a href="https://www.reddit.com/r/i3wm/">FAQ</a></li>
<li><a href="/contact">Contact</a></li>
<li><a href="http://bugs.i3wm.org/">Bugs</a></li>
<li><a href="https://bugs.i3wm.org/">Bugs</a></li>
</ul>
<br style="clear: both">
<div id="content" class="pod">

2
docs/i3bar-protocol
View File

@ -96,7 +96,7 @@ i3status and others will output single statuslines in one line, separated by
You can find an example of a shell script which can be used as your
+status_command+ in the bar configuration at
http://code.stapelberg.de/git/i3/tree/contrib/trivial-bar-script.sh?h=next
https://github.com/i3/i3/blob/next/contrib/trivial-bar-script.sh
=== Header in detail

8
docs/layout-saving
View File

@ -52,7 +52,7 @@ it will be placed in the corresponding placeholder window. We say it gets
Note: Swallowing windows into unsatisfied placeholder windows takes precedence
over
link:http://i3wm.org/docs/userguide.html#_automatically_putting_clients_on_specific_workspaces[assignment
link:https://i3wm.org/docs/userguide.html#_automatically_putting_clients_on_specific_workspaces[assignment
rules]. For example, if you assign all Emacs windows to workspace 1 in your i3
configuration file, but there is a placeholder window on workspace 2 which
matches Emacs as well, your newly started Emacs window will end up in the
@ -164,7 +164,7 @@ a Chrome window:
image:layout-saving-1.png["Restored layout",width=400,link="layout-saving-1.png"]
The structure of this JSON file looks a lot like the +TREE+ reply, see
http://build.i3wm.org/docs/ipc.html#_tree_reply for documentation on that. Some
https://build.i3wm.org/docs/ipc.html#_tree_reply for documentation on that. Some
properties are excluded because they are not relevant when restoring a layout.
Most importantly, look at the "swallows" section of each window. This is where
@ -229,8 +229,8 @@ Both deviations from the JSON standard are to make manual editing by humans
easier. In case you are writing a more elaborate tool for manipulating these
layouts, you can either use a JSON parser that supports these deviations (for
example libyajl), transform the layout file to a JSON-conforming file, or
link:http://cr.i3wm.org/[submit a patch] to make +i3-save-tree(1)+ optionally
output standard-conforming JSON.
link:https://github.com/i3/i3/blob/next/.github/CONTRIBUTING.md[submit a patch]
to make +i3-save-tree(1)+ optionally output standard-conforming JSON.
== Troubleshooting

2
docs/refcard.html
View File

@ -34,7 +34,7 @@
<header>
<img id="logo" src="logo-30.png" alt="" />
<h1>i3 Reference Card</h1>
<a href="http://i3wm.org/docs/userguide.html">http://i3wm.org/docs/userguide.html</a>
<a href="https://i3wm.org/docs/userguide.html">https://i3wm.org/docs/userguide.html</a>
<p>
Throughout this guide, the i3 logo will be used to refer to the configured modifier.
This is the <kbd></kbd> key (<code>Mod1</code>) by default,

10
docs/testsuite
View File

@ -41,10 +41,10 @@ Apart from this document, you should also have a look at:
http://onyxneon.com/books/modern_perl/modern_perl_a4.pdf
2. The latest Perl documentation of the "i3test" (general testcase setup) and
"i3test::Test" (additional test instructions) modules:
http://build.i3wm.org/docs/lib-i3test.html respectively
http://build.i3wm.org/docs/lib-i3test-test.html
https://build.i3wm.org/docs/lib-i3test.html respectively
https://build.i3wm.org/docs/lib-i3test-test.html
3. The latest documentation on i3’s IPC interface:
http://build.i3wm.org/docs/ipc.html
https://build.i3wm.org/docs/ipc.html
== Implementation
@ -99,7 +99,7 @@ $ sudo cpan .
--------------------------------------------------------------------------------
In case you don’t have root permissions, you can also install into your home
directory, see http://michael.stapelberg.de/cpan/
directory, see https://michael.stapelberg.de/cpan/
=== Mechanisms
@ -240,7 +240,7 @@ interface which i3 provides. It is used for the startup process of i3, for
terminating it cleanly and (most importantly) for modifying and getting the
current state (layout tree).
See [http://i3wm.org/docs/ipc.html] for documentation on the IPC interface.
See [https://i3wm.org/docs/ipc.html] for documentation on the IPC interface.
==== X11::XCB

6
docs/userguide
View File

@ -802,7 +802,7 @@ The first part of the WM_CLASS is the instance ("irssi" in this example), the
second part is the class ("URxvt" in this example).
Should you have any problems with assignments, make sure to check the i3
logfile first (see http://i3wm.org/docs/debugging.html). It includes more
logfile first (see https://i3wm.org/docs/debugging.html). It includes more
details about the matching process and the window’s actual class, instance and
title when starting up.
@ -1056,7 +1056,7 @@ force_focus_wrapping yes
=== Forcing Xinerama
As explained in-depth in <http://i3wm.org/docs/multi-monitor.html>, some X11
As explained in-depth in <https://i3wm.org/docs/multi-monitor.html>, some X11
video drivers (especially the nVidia binary driver) only provide support for
Xinerama instead of RandR. In such a situation, i3 must be told to use the
inferior Xinerama API explicitly and therefore don’t provide support for
@ -2448,7 +2448,7 @@ bindsym $mod+u border none
[[shmlog]]
=== Enabling shared memory logging
As described in http://i3wm.org/docs/debugging.html, i3 can log to a shared
As described in https://i3wm.org/docs/debugging.html, i3 can log to a shared
memory buffer, which you can dump using +i3-dump-log+. The +shmlog+ command
allows you to enable or disable the shared memory logging at runtime.

2
docs/wsbar
View File

@ -48,7 +48,7 @@ will be adjusted properly.
+i3-wsbar+ used to be the reference implementation before we had +i3bar+.
Nowadays, it is not shipped with release tarballs, but you can still get it at
http://code.stapelberg.de/git/i3/tree/contrib/i3-wsbar
https://github.com/i3/i3/blob/next/contrib/i3-wsbar
=== The big picture