summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--HACKING4
-rw-r--r--NEWS2
-rw-r--r--docs/caja-autorun-software.14
-rw-r--r--docs/caja-connect-server.14
-rw-r--r--docs/caja-file-management-properties.14
-rw-r--r--docs/caja.14
-rw-r--r--docs/recommended-books.html64
-rw-r--r--docs/style-guide.html2
-rw-r--r--icons/audio.svg4
-rw-r--r--libcaja-private/caja-autorun.c2
-rw-r--r--libcaja-private/caja-file-operations.c2
-rw-r--r--libcaja-private/caja-file.c2
-rw-r--r--src/caja-autorun-software.c2
-rw-r--r--src/file-manager/fm-icon-view.c2
-rwxr-xr-xupdate-authors.pl2
15 files changed, 52 insertions, 52 deletions
diff --git a/HACKING b/HACKING
index 4d767567..6a745cc3 100644
--- a/HACKING
+++ b/HACKING
@@ -3,6 +3,6 @@ Hacking on Caja
The Caja source tree is available from MATE git
(https://github.com/mate-desktop/caja) and
-in releases on the MATE FTP site (http://pub.mate-desktop.org/).
+in releases on the MATE FTP site (https://pub.mate-desktop.org/).
-See also http://wiki.mate-desktop.org/applications:caja .
+See also https://wiki.mate-desktop.org/applications:caja .
diff --git a/NEWS b/NEWS
index c2340308..429afa65 100644
--- a/NEWS
+++ b/NEWS
@@ -498,7 +498,7 @@
* Replace mateconf with gsettings (much code taken from Nautilus 3.0 patches by Alexander Larsson)
* "Show backup files" option merged in "Show hidden files"
- * Add support for freedesktop.org File Manager DBus Interface (http://www.freedesktop.org/wiki/Specifications/file-manager-interface)
+ * Add support for freedesktop.org File Manager DBus Interface (https://www.freedesktop.org/wiki/Specifications/file-manager-interface)
* Allow to open files, if passed as arguments
### caja 1.3.0
diff --git a/docs/caja-autorun-software.1 b/docs/caja-autorun-software.1
index 51d87a29..94543ee9 100644
--- a/docs/caja-autorun-software.1
+++ b/docs/caja-autorun-software.1
@@ -23,13 +23,13 @@ caja-autorun-software \- Autorun Software in Caja
This executable is provided as a part of the Caja package for the MATE Desktop Environment.
.SH "BUGS"
.SS Should you encounter any bugs, they may be reported at:
-http://github.com/mate-desktop/caja/issues
+https://github.com/mate-desktop/caja/issues
.SH "LICENSE"
GPL v2 or later
.SH "SEE ALSO"
.SS
Caja documentation can be found from the "Help" menu, or by pressing the F1 key.
-Further information may also be available at: http://wiki.mate-desktop.org/docs
+Further information may also be available at: https://wiki.mate-desktop.org/docs
.P
.BR "caja" (1),
.BR "caja-connect-server" (1),
diff --git a/docs/caja-connect-server.1 b/docs/caja-connect-server.1
index 716134b0..ea169a0e 100644
--- a/docs/caja-connect-server.1
+++ b/docs/caja-connect-server.1
@@ -26,14 +26,14 @@ Print standard command line options.
Print all command line options.
.SH "BUGS"
.SS Should you encounter any bugs, they may be reported at:
-http://github.com/mate-desktop/caja/issues
+https://github.com/mate-desktop/caja/issues
.SH "AUTHORS"
.SS This Man Page has been written for the MATE Desktop Environment by:
Adam Erdman <[email protected]> (2014)
.SH "SEE ALSO"
.SS
Caja documentation can be found from the "Help" menu, or by pressing the F1 key.
-Further information may also be available at: http://wiki.mate-desktop.org/docs
+Further information may also be available at: https://wiki.mate-desktop.org/docs
.P
.BR "caja" (1),
.BR "caja-autorun-software" (1),
diff --git a/docs/caja-file-management-properties.1 b/docs/caja-file-management-properties.1
index d5cc77b5..d38135d8 100644
--- a/docs/caja-file-management-properties.1
+++ b/docs/caja-file-management-properties.1
@@ -14,14 +14,14 @@ File Management Preferences allows the user to configure the way caja behaves.
You can specify appearance preferences for the Default View; and defaults for Icon, Compact, List, and Tree View; and select sort options and display options. You can configure Caja to recognize Single or Double Click input; as well as Include a Delete command and menu option that bypasses the Trash. Caja File Management Preferences (\fBcaja-file-management-properties\fR) also allows you to tell Caja how to handle certain files; whether to View or Run executable text files; Automatically view or play Media like CDs, DVDs, or photos, and which applications to use when performing these tasks. Among some other options, this dialog also allows you to adjust file-preview settings, and settings for installed plugins if they exist.
.SH "BUGS"
.SS Should you encounter any bugs, they may be reported at:
-http://github.com/mate-desktop/caja/issues
+https://github.com/mate-desktop/caja/issues
.SH "AUTHORS"
.SS This Man Page has been written for the MATE Desktop Environment by:
Adam Erdman <[email protected]> (2014)
.SH "SEE ALSO"
.SS
Caja documentation can be found from the "Help" menu, or by pressing the F1 key.
-Further information may also be available at: http://wiki.mate-desktop.org/docs
+Further information may also be available at: https://wiki.mate-desktop.org/docs
.P
.BR "caja" (1),
.BR "caja-autorun-software" (1),
diff --git a/docs/caja.1 b/docs/caja.1
index f77fab6c..6fc37340 100644
--- a/docs/caja.1
+++ b/docs/caja.1
@@ -68,7 +68,7 @@ Open a Caja window in "user's" home directory without managing the desktop.
Open a Caja window that is 600 pixels wide by 400 pixels high.
.SH "BUGS"
.SS Should you encounter any bugs, they may be reported at:
-http://github.com/mate-desktop/caja/issues
+https://github.com/mate-desktop/caja/issues
.SH "AUTHORS"
.SS This Man Page has been updated/re-written for the MATE Desktop Environment by:
Adam Erdman <[email protected]> (2014)
@@ -77,7 +77,7 @@ This manual page was originally written by Takuo KITAME <[email protected]> and
.SH "SEE ALSO"
.SS
Caja documentation can be found from the "Help" menu, or by pressing the F1 key.
-Further information may also be available at: http://wiki.mate-desktop.org/docs
+Further information may also be available at: https://wiki.mate-desktop.org/docs
.P
.BR "caja-file-management-properties" (1),
.BR "caja-autorun-software" (1),
diff --git a/docs/recommended-books.html b/docs/recommended-books.html
index cedf95ab..281b4992 100644
--- a/docs/recommended-books.html
+++ b/docs/recommended-books.html
@@ -25,14 +25,14 @@ I've picked out a small number of extremely useful books so you won't have to wa
C++ standard itself also contain useful introductory material. For some
programmers, these are enough to explain the features of the language.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201889544/dianepattersonstA"><b><i>The C++ Programming Language, Third Edition</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201889544/dianepattersonstA"><b><i>The C++ Programming Language, Third Edition</i></b></a>,
Bjarne Stroustrup. This is the book by the creator of the C++ language. This third edition is far superior
to the first two, and covers the ISO Standard version of the language in detail, including the library.
Any serious C++ programmer should read this book. There have been many corrections since the first printing, so get
the newest printing you can. Bjarne has <a href="http://www.research.att.com/~bs/3rd.html">supporting materials</a>
for the book on the web, including the errata lists that enumerate all changes between printings.</p>
-<p><a name="Josuttis" href="http://www.amazon.com/exec/obidos/ASIN/0201379260/dianepattersonstA"><b><i>The C++ Standard Library</i></b></a>,
+<p><a name="Josuttis" href="https://www.amazon.com/exec/obidos/ASIN/0201379260/dianepattersonstA"><b><i>The C++ Standard Library</i></b></a>,
Nicolai M. Josuttis. This book has the best coverage of the library. There have been tons of others that cover
the library, or focus on the STL or streams. But Josuttis covers all these subjects better than any of his
predecessors. Since we use the library extensively in Eazel projects, this is a must read.
@@ -45,27 +45,27 @@ They can help you understand idioms you'll find in our code.
This kind of idiomatic programming is important in C++, because the language
gives you so much freedom to write unusable, unmaintainable code.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201615622/dianepattersonstA"><b><i>Exceptional C++</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201615622/dianepattersonstA"><b><i>Exceptional C++</i></b></a>,
Herb Sutter. This is a collection of material that was originally part of Herb's
<a href="http://www.peerdirect.com/resources"><i>Guru of the Week</i></a>. This includes much of the most
advanced C++ information available. I learned many of the most important techniques from Herb, including
the swap technique for writing safe assignment operators. Herb covers each topic thoroughly.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201423391/dianepattersonstA"><b><i>Ruminations on C++</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201423391/dianepattersonstA"><b><i>Ruminations on C++</i></b></a>,
Andrew Koenig and Barbara Moo.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201924889/dianepattersonstA"><b><i>Effective C++, Second Edition</i></b></a>
-and <a href="http://www.amazon.com/exec/obidos/ASIN/020163371X/dianepattersonstA"><b><i>More Effective C++</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201924889/dianepattersonstA"><b><i>Effective C++, Second Edition</i></b></a>
+and <a href="https://www.amazon.com/exec/obidos/ASIN/020163371X/dianepattersonstA"><b><i>More Effective C++</i></b></a>,
Scott Meyers. These books contain a laundry list of important C++ idioms. The books are a bit less
important now than when they were first released, but still full of valuable stuff. There's also a
-<a href="http://www.amazon.com/exec/obidos/ASIN/0201310155/dianepattersonstA">CD edition</a>
+<a href="https://www.amazon.com/exec/obidos/ASIN/0201310155/dianepattersonstA">CD edition</a>
(there's a <a href="http://mox.eazel.com/mec">copy</a> of it on Rob's machine)
that contains both books in electronic form. The publisher's web site has a good collection of
supporting materials for both
<a href="http://cseng.aw.com/bookdetail.qry?ISBN=0-201-92488-9">the original</a> and
<a href="http://cseng.aw.com/bookdetail.qry?ISBN=0-201-63371-X">the second book</a></p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201543303/dianepattersonstA"><b><i>The Design and Evolution of C++</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201543303/dianepattersonstA"><b><i>The Design and Evolution of C++</i></b></a>,
Bjarne Stroustrup. While this book doesn't prescribe any specific techniques, it will help you understand the
tradeoffs behind all the language features, and how C++ got to be what it is. I highly recommend it.</p>
@@ -74,7 +74,7 @@ tradeoffs behind all the language features, and how C++ got to be what it is. I
<p>These books explain C++ programming from scratch. These particular examples are so good that they
can be useful even for experienced programmers who already know C++ well.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201485184/dianepattersonstA"><b><i>Essential C++</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201485184/dianepattersonstA"><b><i>Essential C++</i></b></a>,
Stanley Lippman. This tutorial is much more useful than the longer and more complete works, like
<a href="#Primer"><i>C++ Primer</i></a>.
It covers the features and the reasons for the features quite well. In particular, it has a good explanation
@@ -84,7 +84,7 @@ of references and pointers and why you'd use one or the other. It covers templat
<p>OK, so I'm not an expert on Gtk yet. But I'm becoming one.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0735700788/dianepattersonstA"><b><i>Gtk+/Mate Application Development</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0735700788/dianepattersonstA"><b><i>Gtk+/Mate Application Development</i></b></a>,
Havoc Pennington. I learned a lot from this book. But it's all Gtk+ and C; things are done
a bit differently with Gtk-- from C++. It's still worth reading.</p>
@@ -92,27 +92,27 @@ a bit differently with Gtk-- from C++. It's still worth reading.</p>
<p>These books are valuable because of the ideas in them, but are not specific to a particular programming language or toolkit.</p>
-<p><a name="Refactoring" href="http://www.amazon.com/exec/obidos/ASIN/0201485672/dianepattersonstA"><b><i>Refactoring</i></b></a>,
+<p><a name="Refactoring" href="https://www.amazon.com/exec/obidos/ASIN/0201485672/dianepattersonstA"><b><i>Refactoring</i></b></a>,
Martin Fowler. This book outlines a philosophy of programming that we embrace at Eazel. The ideas
about changing existing code to improve it so it can be modified are extremely important. The ideas
about unit testing as a means to this end shape the way we use unit testing at Eazel.
All the examples in the book are in Java, but the ideas apply well to C++.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/020161586X/dianepattersonstA"><b><i>The Practice of Programming</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/020161586X/dianepattersonstA"><b><i>The Practice of Programming</i></b></a>,
Brian Kernighan, Rob Pike. This book, by two of the most famous UNIX programmers, covers a lot of basic
programming smarts. I don't agree with everything they have to say, but the book is great as a whole.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201657880/dianepattersonstA"><b><i>Programming Pearls, Second Edition</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201657880/dianepattersonstA"><b><i>Programming Pearls, Second Edition</i></b></a>,
Jon Bentley. This classic has recently been updated with a second edition. I haven't read the second edition
yet, but I'm sure it's great. When I read it, I'll put more specific comments here.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201633612/dianepattersonstA"><b><i>Design Patterns</i></b></a>.
-There's also a <a href="http://www.amazon.com/exec/obidos/ASIN/0201634988/dianepattersonstA">CD edition</a>
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201633612/dianepattersonstA"><b><i>Design Patterns</i></b></a>.
+There's also a <a href="https://www.amazon.com/exec/obidos/ASIN/0201634988/dianepattersonstA">CD edition</a>
(there's a <a href="http://mox.eazel.com/dp">copy</a> of it on Rob's machine).</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201350882/dianepattersonstA"><b><i>Algorithms in C++, Third Edition</i></b></a>,
-Robert Sedgewick. The <a href="http://www.amazon.com/exec/obidos/ASIN/0201314525/dianepattersonstA">original version</a> is in C.
-There's also an upcoming <a href="http://www.amazon.com/exec/obidos/ASIN/0201361205/dianepattersonstA">Java version</a>.</p>
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201350882/dianepattersonstA"><b><i>Algorithms in C++, Third Edition</i></b></a>,
+Robert Sedgewick. The <a href="https://www.amazon.com/exec/obidos/ASIN/0201314525/dianepattersonstA">original version</a> is in C.
+There's also an upcoming <a href="https://www.amazon.com/exec/obidos/ASIN/0201361205/dianepattersonstA">Java version</a>.</p>
<h2>Books I Have Read, But Do Not Recommend</h2>
@@ -121,46 +121,46 @@ Here are a few that were not as exemplary. I won't try to sort out the ones that
from the truly awful. If you see a book that's not on this list, it might be one I'd recommend. Maybe
I haven't read it.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201498413/dianepattersonstA"><b><i>C Interfaces and Implementations</i></b></a>.</p>
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201498413/dianepattersonstA"><b><i>C Interfaces and Implementations</i></b></a>.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201596415/dianepattersonstA"><b><i>C++ IOStreams Handbook</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201596415/dianepattersonstA"><b><i>C++ IOStreams Handbook</i></b></a>,
Steve Teale. <a href="Josuttis">Josuttis</a> covers streams better.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201616416/dianepattersonstA"><b><i>Extreme Programming Explained</i></b></a>.
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201616416/dianepattersonstA"><b><i>Extreme Programming Explained</i></b></a>.
My love for <a href="Refactoring"><i>Refactoring</i></a> had me excited about this one, but it was a disappointment.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201309564/dianepattersonstA"><b><i>Generic Programming and the STL</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201309564/dianepattersonstA"><b><i>Generic Programming and the STL</i></b></a>,
Matt Austern. I don't know of anyone who knows more about the STL than Matt Austern, who's currently
maintaining the main implementation at SGI. But <a href="Josuttis">Josuttis</a> covers the STL better.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0131209655/dianepattersonstA"><b><i>Industrial Strength C++</i></b></a>.</p>
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0131209655/dianepattersonstA"><b><i>Industrial Strength C++</i></b></a>.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201834545/dianepattersonstA"><b><i>Inside the C++ Object Model</i></b></a>.</p>
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201834545/dianepattersonstA"><b><i>Inside the C++ Object Model</i></b></a>.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201633620/dianepattersonstA"><b><i>Large-Scale C++ Software Design</i></b></a>,
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201633620/dianepattersonstA"><b><i>Large-Scale C++ Software Design</i></b></a>,
John Lakos.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0130142697/dianepattersonstA"><b><i>Objects Unencapsulated: Java, Eiffel and C++??</i></b></a>.
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0130142697/dianepattersonstA"><b><i>Objects Unencapsulated: Java, Eiffel and C++??</i></b></a>.
This is a basically an "Eiffel is great, C++ sucks" book. Some interesting insights, but a lot of sloppy thinking.</p>
<h2>Books That Need Review</h2>
<p>This is a list of possibly important books that I haven't checked out yet.</p>
-<p><a name="Primer" href="http://www.amazon.com/exec/obidos/ASIN/0201824701/dianepattersonstA"><b><i>C++ Primer, Third Edition</i></b></a>,
+<p><a name="Primer" href="https://www.amazon.com/exec/obidos/ASIN/0201824701/dianepattersonstA"><b><i>C++ Primer, Third Edition</i></b></a>,
Stanley Lippman, Josee Lajoie. The earlier editions were good but not great. But I have reason
to believe that this one might be better than those were.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201309939/dianepattersonstA"><b><i>C++ Primer Answer Book</i></b></a>.
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201309939/dianepattersonstA"><b><i>C++ Primer Answer Book</i></b></a>.
I checked, and this answer book does go with the third edition of <i>C++ Primer</i>.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0201309599/dianepattersonstA"><b><i>Design Patterns and Contracts</i></b></a>.</p>
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0201309599/dianepattersonstA"><b><i>Design Patterns and Contracts</i></b></a>.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0735700214/dianepattersonstA"><b><i>Developing Linux Applications with GTK+ and GDK</i></b></a>.</p>
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0735700214/dianepattersonstA"><b><i>Developing Linux Applications with GTK+ and GDK</i></b></a>.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0764546406/dianepattersonstA"><b><i>Linux Mate/Gtk Programming Bible</i></b></a>.</p>
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0764546406/dianepattersonstA"><b><i>Linux Mate/Gtk Programming Bible</i></b></a>.</p>
-<p><a href="http://www.amazon.com/exec/obidos/ASIN/0672318296/dianepattersonstA"><b><i>Sams Teach Yourself Gtk+ Programming in 21 Days</i></b></a>.</p>
+<p><a href="https://www.amazon.com/exec/obidos/ASIN/0672318296/dianepattersonstA"><b><i>Sams Teach Yourself Gtk+ Programming in 21 Days</i></b></a>.</p>
</body>
diff --git a/docs/style-guide.html b/docs/style-guide.html
index 8215456d..e4f67ed0 100644
--- a/docs/style-guide.html
+++ b/docs/style-guide.html
@@ -9,7 +9,7 @@
<p>To make code written for Caja look and act in a predictable way,
we follow a set of guidelines that specify some details of how we write code.
To start, we follow all the guidelines outlined in the
-<a href="http://developer.gnome.org/doc/guides/programming-guidelines/">MATE Programming Guidelines</a>.</p>
+<a href="https://developer.gnome.org/programming-guidelines/stable/">MATE Programming Guidelines</a>.</p>
<p>This document covers both things that are not mentioned in the MATE
Programming Guidelines and things that are mentioned there but need
diff --git a/icons/audio.svg b/icons/audio.svg
index 4c25d4ba..8d40aff1 100644
--- a/icons/audio.svg
+++ b/icons/audio.svg
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<!-- Created with Inkscape (https://www.inkscape.org/) -->
<svg xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" width="28" height="28" id="svg2" version="1.1" inkscape:version="0.47 r22583" sodipodi:docname="New document 1">
<defs id="defs4">
<linearGradient inkscape:collect="always" id="linearGradient3793">
@@ -40,4 +40,4 @@
<path style="color: rgb(0, 0, 0); fill: rgb(255, 255, 255); fill-opacity: 1; fill-rule: nonzero; stroke: none; stroke-width: 1; marker: none; visibility: visible; display: inline; overflow: visible;" d="m 530.28181,487.375 c -0.29406,10e-4 -0.28174,0.28275 -0.28174,0.28275 l 0,8.45479 c 0,0 -0.004,0.24964 0.25,0.24964 l 0.23437,0 4.51556,-4.50919 -4.47058,-4.47894 c 0,0 -0.24761,9.5e-4 -0.24761,9.5e-4 z" id="path3869" sodipodi:nodetypes="cccccccs" inkscape:export-filename="/home/hbons/Dropbox/Public/play.png" inkscape:export-xdpi="90" inkscape:export-ydpi="90"/>
</g>
</g>
-</svg> \ No newline at end of file
+</svg>
diff --git a/libcaja-private/caja-autorun.c b/libcaja-private/caja-autorun.c
index 797e608b..a7b040c6 100644
--- a/libcaja-private/caja-autorun.c
+++ b/libcaja-private/caja-autorun.c
@@ -428,7 +428,7 @@ caja_autorun_rebuild_combo_box (GtkWidget *combo_box)
*
* We need the API outlined in
*
- * http://bugzilla.gnome.org/show_bug.cgi?id=545350
+ * https://bugzilla.gnome.org/show_bug.cgi?id=545350
*
* to do this.
*
diff --git a/libcaja-private/caja-file-operations.c b/libcaja-private/caja-file-operations.c
index db29862f..ecd922a3 100644
--- a/libcaja-private/caja-file-operations.c
+++ b/libcaja-private/caja-file-operations.c
@@ -2093,7 +2093,7 @@ trash_or_delete_internal (GList *files,
}
// Start UNDO-REDO
// FIXME: Disabled, because of missing mechanism to restore a file from trash in a clean way
- // see http://www.mail-archive.com/[email protected]/msg04664.html
+ // see https://www.mail-archive.com/[email protected]/msg04664.html
if (try_trash && !caja_undostack_manager_is_undo_redo(caja_undostack_manager_instance())) {
job->common.undo_redo_data = caja_undostack_manager_data_new (CAJA_UNDOSTACK_MOVETOTRASH, g_list_length(files));
GFile* src_dir = g_file_get_parent (files->data);
diff --git a/libcaja-private/caja-file.c b/libcaja-private/caja-file.c
index 51c9e6db..dcef27e8 100644
--- a/libcaja-private/caja-file.c
+++ b/libcaja-private/caja-file.c
@@ -602,7 +602,7 @@ add_to_link_hash_table_list (GList **list, CajaFile *file)
{
if (g_list_find (*list, file) != NULL) {
g_warning ("Adding file to symlink_table multiple times. "
- "Please add feedback of what you were doing at http://bugzilla.gnome.org/show_bug.cgi?id=358172\n");
+ "Please add feedback of what you were doing at https://bugzilla.gnome.org/show_bug.cgi?id=358172\n");
return;
}
g_object_weak_ref (G_OBJECT (file), symbolic_link_weak_notify, list);
diff --git a/src/caja-autorun-software.c b/src/caja-autorun-software.c
index 019cb5c6..ec2ccf74 100644
--- a/src/caja-autorun-software.c
+++ b/src/caja-autorun-software.c
@@ -110,7 +110,7 @@ autorun (GMount *mount)
/* Careful here, according to
*
- * http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html
+ * https://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html
*
* the ordering does matter.
*/
diff --git a/src/file-manager/fm-icon-view.c b/src/file-manager/fm-icon-view.c
index baa4394d..c70bea4a 100644
--- a/src/file-manager/fm-icon-view.c
+++ b/src/file-manager/fm-icon-view.c
@@ -576,7 +576,7 @@ fm_icon_view_remove_file (FMDirectoryView *view, CajaFile *file, CajaDirectory *
model_uri = caja_directory_get_uri (fm_directory_view_get_model (view));
g_warning ("fm_icon_view_remove_file() - directory not icon view model, shouldn't happen.\n"
"file: %p:%s, dir: %p:%s, model: %p:%s, view loading: %d\n"
- "If you see this, please add this info to http://bugzilla.gnome.org/show_bug.cgi?id=368178",
+ "If you see this, please add this info to https://bugzilla.gnome.org/show_bug.cgi?id=368178",
file, file_uri, directory, dir_uri, fm_directory_view_get_model (view), model_uri, fm_directory_view_get_loading (view));
g_free (file_uri);
g_free (dir_uri);
diff --git a/update-authors.pl b/update-authors.pl
index c2a52109..8814bc3f 100755
--- a/update-authors.pl
+++ b/update-authors.pl
@@ -14,7 +14,7 @@
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
- along with Caja. If not, see <http://www.gnu.org/licenses/>.
+ along with Caja. If not, see <https://www.gnu.org/licenses/>.
=cut
use strict;