Nicolas Goaziou writes:
> Rasmus writes:
>
>> It's a special block, so e.g. org-latex-special-block. But contents is
>> already transcoded by the time in arrives to e.g. org-latex-special-block.
>> To the extend this should be fixed, one way would be to allow a ra
I think
it has to do with the Meta. Other Meta bindings use ?\e and the numeric
value that is picked up for \M-a is pretty large... Sometimes I managed
to get org-backward-sentence in the orgstruct-mode-map, but it just wans't
picked up.
Any hints would be appreciated.
Rasmus
My test:
Nicolas Goaziou writes:
> You can use `advice-add' in this case.
Or just add-function.
*I* can solve it one way or the other. But that does not
necessarily mean that it's not a bug. And that was the question.
—Rasmus
--
. . . It begins of course with The Internet. A Net of Peers
er to capitalize a word. I could
maintain my own copy of the package, though.
I guess we could, and maybe should, remap the function in orgstruct modes.
Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
is
already transcoded by the time in arrives to e.g. org-latex-special-block.
To the extend this should be fixed, one way would be to allow a raw option
to special blocks (also needed for e.g. #+{begin,end}_equation) and have
babel insert it as needed. I don't know how easy this is.
Rasmus
--
I feel emotional landscapes they puzzle me
ining the orgmode.org server and taking care of errors when
>updating Worg (1 hour per month).
>
> 4. Merging the last stable release into Emacs repository. (1 hour
>every release).
>
> 5. Releasing Org (.5 hour every release).
I can help with 2, 4 *OR* 5 as you prefe
Hi,
Sorry for bringing this thread up again.
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Forget about fill-paragraph. Try this with test-org as nil and non-nil:
>>
>> (let ((test-org nil))
>> (switch-to-buffer "test.org")
>> (if test-
\end{Program}
> #+END_LaTeX
>
> There must be better ways of doing this?
Maybe something like this
#+latex_header: \floatstyle{ruled}
#+latex_header: \newfloat{program}{tbp}{lop}[section]
#+caption: my program
#+begin_program
#+BEGIN_SRC sh
./somescripts.sh someargs
#+
he box. Can you reproduce the error from emacs -q?
Which if your version of Org? Do you have internet on your test computer?
Rasmus
--
And I faced endless streams of vendor-approved Ikea furniture. . .
Matt Price writes:
> Did you try this:
>
> (setcdr (assq 'system org-file-apps-defaults-gnu ) '(call-process
> "xdg-open" nil 0 nil file))
>
> That works for me.
It works for odt, but not html.
--
Slowly unravels in a ball of yarn and the devil collects it
Marco Wahl writes:
> Rasmus writes:
>
>>> IIUC org-eww is missing because it is not included in branch 'maint'.
>>> Possibly it is a good idea to put org-eww there.
>>
>> In the lisp folder, maint is typically for bug fixes. I guess for contrib
>
ng the DESKTOP_SESSION in either the shell starting Emacs or via
setenv.
So I guess on could use an xdg-open alternative or hardcode programs in
mailcap...
Rasmus
--
A page of history is worth a volume of logic
Rasmus writes:
> The attached patch re-enables breaks in region four of
> org-complex-heading-regexp, i.e. from the cookie up to tags. A quick test
> suggests it works nicely.
Pushed. Let me know if it's worse than before.
Rasmus
--
Need more coffee. . .
Rasmus writes:
> Nicolas Goaziou writes:
>
>> Also, shouldn't the final (delete-indentation ARG) be in the "else" part
>> of the `if'?
>
> It was, at least on my disk. I did not check the patch.
>
>>> +(ert-deftest test-org-delete-
00548.html
Otherwise you could use e.g. imagemagick to stick together figures.
—Rasmus
--
Need more coffee. . .
Suvayu Ali writes:
> On Wed, May 20, 2015 at 11:50:03AM +0200, Rasmus wrote:
>> Suvayu Ali writes:
>>
>
>> > Do you have a mailcap which says otherwise? That's what I would suspect
>> > given the doc string for org-file-apps and the default value
rks as expected from the
terminal.
—Rasmus
--
May contains speling mistake
's hardcoded in org-latex--inline-image.
Thus, the easiest thing may be to use a filter and be sure to include the
pdf extension. I think you might have to use
org-export-filter-paragraph-functions,
Hope it helps,
Rasmus
--
Dung makes an excellent fertilizer
Marco Wahl writes:
> IIUC org-eww is missing because it is not included in branch 'maint'.
> Possibly it is a good idea to put org-eww there.
In the lisp folder, maint is typically for bug fixes. I guess for contrib
it's more flexible.
—Rasmus
--
⠠⠵
Mark Edgington writes:
> Rasmus gmx.us> writes:
>>
>> It was fixed a while ago in master. Are you using 8.2?
>
>
> Oh, I thought I was using something more recent, since the version was named
> "8.3beta", but apparently that's old. Thanks!
Jacob Gerlach writes:
> Hello,
>
> On Tue, May 19, 2015 at 11:29 AM, Rasmus wrote:
>> If I explicitly eval:
>>
>> (org-babel-do-load-languages 'org-babel-load-languages '((sh . t)))
>> (setq org-latex-custom-lang-environments '((sh
-latex-custom-lang-environments '((sh "myverbatim"))
org-latex-listings t)
And export
#+BEGIN_SRC sh :exports code
echo "Hello"
#+END_SRC
I get the the block wrapped in the desired environment. I don't know why
your local variables are ignored, but it seems
llowing stackoverflow page suggests the issue is in ox-odt.el:
With your change it open the odt file as a tar-mode file from Emacs -q.
Without your change it doesn't open it at all. BTW: My Emacs also doesn't
open html exports in Fx files when I use C-c C-e h-o. I never tried to
debug it though...
Rasmus
--
9000!
You are using a patch I sent to the list which removed this by
accident. If you remove that patch everything will be OK.
Sorry about that Titus.
Rasmus
--
Together we will make the possible totay impossible!
in master. Are you using 8.2?
Rasmus
--
Together we'll stand, divided we'll fall
> for replacing inlinetasks with something else (i.e., change syntax),
> albeit this is no simple task.
I don't particularly care for them either.
—Rasmus
--
This space is left intentionally blank
Eric S Fraga writes:
> On Monday, 18 May 2015 at 15:16, Rasmus wrote:
>> Nicolas Goaziou writes:
>>> I don't know what is a TODO functionality since you suggest to not make
>>> it appear in the agenda.
>>
>> E.g. "Sentence about BAR [TODO: add r
t to be able to mark exactly which part of the document you're
> annotating.
I agree they are different.
> [TODO: ...] cannot do that.
Its virtues are compactness, being similar to a list, being C-k friendly,
and, IMO, more intuitive.
–Rasmus
--
There are known knowns; there are things we know that we know
(mapc (lambda (key)
(org-defkey org-mode-map key nil))
(list [(control return)]
[(shift control return)]
[(meta return)])
—Rasmus
--
It was you, Jezebel, it was you
iew session say, to
>> have the notes so "far away" from the text? Perhaps not with the right
>> helping tools.
>
> Again, not with proper tooling, e.g, remote editing like footnotes.
But this is a change to the *format*, not its principal editor.
—Rasmus
--
Er du tosset for noge' lårt!
review session say, to
have the notes so "far away" from the text? Perhaps not with the right
helping tools.
—Rasmus
> ID is expected to be unique, and consists of alphanumeric characters
> only. Markers are allowed anywhere standard syntax is (e.g., paragraphs,
> verse
Nicolas Goaziou writes:
> That leads me to the next question: should we really mess with this?
Maybe not. Perhaps there's a reason for the current implementation.
—Rasmus
--
. . . It begins of course with The Internet. A Net of Peers
ng-regexp.
> Jumping to the next line is actually counter intuitive, as this is pure
> movement.
It's what it does in tables (most of the time). What would be better?
—Rasmus
--
However beautiful the theory, you should occasionally look at the evidence
Hi Jarmo,
Jarmo Hurri writes:
> Rasmus writes:
>> With your behavior you can (i) break the TODO tag; (ii) break the cookie;
>> (iii) break the tag. At least (i) and (ii) are quite destructive.
>
> I am not sure what you mean, since a single undo will always heal the
>
d,
> are implemented?
FWIW, I did not like the syntax Nicolas suggested in that thread. It
reminded me too much of *XML (which is also true with inlinetasks BTW).
[I, did, however, only add a star to the thread rather than replying].
—Rasmus
--
I hear there's rumors on the, uh, Internets. . .
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Consider this example:
>>
>> |---+---+---|
>> | a | b | c |
>> | d | e | f |
>> |---+---+---|
>> | 1 | 2 | 3 |
>> | 4 | 5 | 6 |
>> |---+---+---|
>> | 5 | 7 | 9
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Can you try the attached patch? It seems to work on my system, but
>> probably more cleanup should be made wrt the "old" outline-functions.
>> + (org-with-wide-buffer
>
s.
Can you try the attached patch? It seems to work on my system, but
probably more cleanup should be made wrt the "old" outline-functions.
—Rasmus
--
This space is left intentionally blank
>From 965aa17b30fd511fbd2f4415104878c52c245550 Mon Sep 17 00:00:00 2001
From: Rasmus
Dat
Eric S Fraga writes:
> Mind you, having played around with emacs -Q and my test file, I have
> run into another bug. If I specify org-indent in the startup options, I
> get a very strange indentation. See attached screenshot. I wonder if
> this is related to my problem?
Probably 'cause you ha
ched patch current column of tags is used if
org-auto-align-tags is nil. Otherwise org-tags-column is used.
I'll push this unless any other undesirable behaviors are found.
Thanks,
Rasmus
--
⠠⠵
>From 112b91cdc2887b1cc4451549dd4dd0c2e6a370ac Mon Sep 17 00:00:00 2001
From: Rasmus
Date: Fri,
more on M-^ and tables if desirable (primarily it should be
moved to org-table, I guess). I can also work more on RET in tables, if
desirable. Another "quirk" that I noticed is that RET works differently
when next row is a hline (insert new row) and a row (move to next row).
This is comple
t me know what you think)
Copyright assignment AND good behavior towards all users, developers and
maintainers of Org is all that is asked.
—Rasmus
--
. . . It begins of course with The Internet. A Net of Peers
Rasmus writes:
> Due to recent controversy about Org being lacking Microsoftesque detail I
> finally implemented org-delete-indentation, which is a function I have
> been missing forever.
Updated patch attached. It now uses (org-fix-tags-on-the-fly). A
consequence of this is that (i)
ersion of the patch and see if you find it more
satisfactory?
Thanks,
Rasmus
--
Governments should be afraid of their people
>From 60688c52732fbbe0757c57686089c55c709f2a07 Mon Sep 17 00:00:00 2001
From: Rasmus
Date: Fri, 15 May 2015 13:08:11 +0200
Subject: [PATCH 1/2] org.el: RET breaks headlin
what I would expect.
Examples:
* foo :tag:
bar|
=> (org-delete-indentation)
* foo bar :tag:
* foo | :tag:
bar
=> (org-delete-indentation t)
* foo bar :tag:
—Rasmus
--
With monopolies the cake is a lie!
>From ef242f5d599d4888cdf57e1f6a65db8406626499 Mon Sep 17 00:00:00
d-position
>
> The `setq' is not necessary here. Bind it within `let' instead.
You are right.
>> + (when (match-beginning 5)
>> +(insert (make-string (length string) ?\
>
> ?\ -> ?\s
>
> If you add this feature, please augment `te
-formulas, though this does not currently support hlines, it
seems.
I have no idea how trivial or hard this is to fix this... But hints or
fixes are appreciated.
—Rasmus
--
The Kids call him Billy the Saint
omplex-heading-regexp, i.e. from the cookie up to tags. A quick test
suggests it works nicely.
WDYT?
—Rasmus
--
However beautiful the theory, you should occasionally look at the evidence
>From 8a2477cb70770526939a6c665026802d46db21ea Mon Sep 17 00:00:00 2001
From: Rasmus
Date: Fri, 15 May 201
g like:
M-x find-library ob- [TAB].
There's also the apropos commands.
Hope it helps,
Rasmus
--
If you can mix business and politics wonderful things can happen!
"Doyley, Marvin M." writes:
> I would like to change the face (i.e., color and appearance) of a
> custom org link type and was wonder if there is a easy way to do this.
I guess you could use highlight-regexp. There's no org-specific way to do it.
—Rasmus
--
Spil noget med Slayer!
Vikas Rawal writes:
> Isn’t \\ in headlines expected to cause a line break?
(member 'line-break (org-element-restriction 'headline)) => nil
I don't know the rational.
—Rasmus
--
May the Force be with you
Ken Mankoff writes:
> Or:
> #+MACRO: NEWLINE @@latex:\\@@ @@html:@@
> #+TITLE: Foo {{{NEWLINE}}} Bar
For some instances of "foo" and "bar", this may be a nicer solution:
#+title: foo
#+subtitle: bar
--
. . . The proofs are technical in nature and provides no real understanding
sign float values. I export to
> WordPress using a zurb foundation based css framework, and my tables were
> all messed up until I figured that out.
I don't know what e.g. zurb foundation means, but perhaps something like
the attached fixes your problem. It's probably a good idea not to
d n is the number of headlines prior to
>> "*Something"...
>
> Sure - this is obvious.
Actually, the error you found is more interesting than what I first
though, as any link with anchors will trigger the error, it seems.
org-publish-cache must be non-nil, which seems to linger on
ctions would no longer be centered as they default to the "left"
class. This could be an issue if this is a good default style...
—Rasmus
--
With monopolies the cake is a lie!
.
* A link to a non existent file
[[file:~/NONEXISTENT.org::#SOMETHING][Link to header in non existing org file]]
—Rasmus
--
Vote for proprietary math!
Paul Harper writes:
> he other thing is in the end I have to convert from the .tex file to a
> .docx file using pandoc
Org exports to odt via ox-odt. You can presumably export directly to docx
using org-odt-convert-processes.
—Rasmus
--
Together we will make the possible tot
ange of
org-string-nw-p which previously relied on "\\S" cf.:
http://article.gmane.org/gmane.emacs.orgmode/95473
> This should be fixed.
Patches welcome. You could try to submit a patch where you add closing
parenthesis characters.
It could even be patches to org.texi!
Thanks,
001\))
($x$) doesn't work. You could use $(x)$. Strangely
org-highlight-latex-and-related still highlights it.
—Rasmus
--
Slowly unravels in a ball of yarn and the devil collects it
Hi Paul,
Paul Harper writes:
> How do I get the preamble above the title?
>
> How do I make the fonts smaller in the title?
>
> I need some items to appear on a page of their own. (ie. Ethical Approval,
> Abstract, Declaration, Table of Contents.) How do I do that?
Do you know KOMA-Scrip? It h
27;cause it's a latex-environment (try running org-element-at-point on
it). You could do
#+begin_myenvironment
"Foo"
#+end_myenvironment
—Rasmus
--
Hvor meget poesi tror De kommer ud af et glas isvand?
Hi,
Eric Abrahamsen writes:
> We're just talking about annotations-plus-metadata here, right? Not
> actual in-text TODOs?
I don't know.
> From what I can tell, rasmus seems to be proposing an in-text TODO,
I mainly extrapolated from your example. Further, I extrapolated
off document?
—Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
like the example. The ordering is weird. Do the first and the
second bracket need to be tied together? Or would something like this
work:
body text to annotate [todo@work: Look this up on the internet]
Or
[todo@work: Look this up on the internet]{body text to annotate}
[todo@work look this up on the internet: body text to annotate]
—Rasmus
--
With monopolies the cake is a lie!
e to ignore it!
> Ah, that's a good point. cl-lib isn't necessary, just convenient, and
> could be removed.
It's only a concern if you want to advocate for including this in Org 8.3.
Cheers,
Rasmus
--
Tack, ni svenska vakttorn. Med plutonium tvingar vi dansken på knä!
y. There's little difference between core and
contrib as neither are included in Emacs and thus are hard to rely on.
Since you use cl-lib (last I checked) it could not be part of Org before
8.4.
Cheers,
Rasmus
--
A page of history is worth a volume of logic
n a footnote reference. C-c C-o can jump between the definition
> and the reference. We can remove C-c '.
I guess that's fine. Still, someone who never uses narrows may find jump
better, especially for short documents. If the org-src window can be
configured to show less than a fullscreen I guess I would have no concerns
with this proposal.
Thanks,
Rasmus
--
There are known knowns; there are things we know that we know
Andreas Hilboll writes:
> Using the current git master, any exported Markdown doesn't include
> title, author, and date information. Is this desired behaviour, or is
> it a bug?
AFAIK it's a "feature".
--
⠠⠵
uivalent, we
> have first-class key bindings to choose from: "C-c C-o", "C-c '", "C-c
> C-c".
C-c C-c would then depend on a defcustom, I guess. At least it's a pity
if C-c C-c only works in some cases, e.g. "if not narrowed".
>> Note that new footnotes currently break the narrow, which is pretty
>> annoying.
>
> I know. This is bad, indeed.
OK.
Rasmus
--
⠠⠵
Vicente Vera writes:
> The patch below changes org-odt-inline-image-rules value, thus
> allowing exported ODT documents to include SVG images by default.
I pushed your change.
Thanks!
Rasmus
--
If you can mix business and politics wonderful things can happen!
ated buffer.
>
> Feedback welcome.
I added this to org.texi.
Note, C-c ' will fail in the following example 'cause the fn definition
does not have contents-end. I started to try fix this but feel free to
beat me to it. I likely will not have time to look more into it until the
weeke
Nicolas Goaziou writes:
>> Here's an updated patch.
>
> Thank you. Some comments follow.
Pushed with your recommendations. Thanks.
--
May the Force be with you
an I get to the state where
this happens from emacs -q?
Thanks,
Rasmus
--
Warning: Everything saved will be lost
have to work with *new* footnotes. Note
that new footnotes currently break the narrow, which is pretty annoying.
Thanks,
Rasmus
--
. . . It begins of course with The Internet. A Net of Peers
use unknown "latex" back-end as a parent
Weird. I can't reproduce this here. Does it happen with emacs -q and,
say, (require 'ox-koma-letter)?
—Rasmus
--
It was you, Jezebel, it was you
minimal example and clear instructions on how
to produce this error? I was unable to reproduce it.
Thanks,
Rasmus
--
El Rey ha muerto. ¡Larga vida al Rey!
e that in this situation, the user is able to widen the
> buffer himself and then jump to the definition in order to edit it. This
> would be a lot of trouble for a debatable benefit.
Sure, but recreating your narrow takes time. And it's annoying when you
want to review a section, say.
—Rasmus
--
And I faced endless streams of vendor-approved Ikea furniture. . .
Rasmus writes:
>1. Retrieve the footnote in the minibuffer. E.g. org-footnote-action
> shows the footnote-definition if it is outside of the narrow (and
> known) in the minibuffer? E.g. 2. when using prefix.
>2. Show the definition in the minibuffer as editabl
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Nicolas Goaziou writes:
>
>> Point is moved, though. If narrow shouldn't be "broken" then point
>> shouldn't be moved. I.e. no move when the definition is not within the
>> buffer.
>
> F
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Nicolas Goaziou writes:
>>>
>>> `org-html--build-mathjax-config' needs to check, in addition to parse
>>> tree, cdr of all associations in (plist-get
>>> info :footnote-definition-alist), and
;smart" can of worms. On the other hand,
unnecessary JS should be avoided at very high costs.
Perhaps it's enough to check is mathjax or latex math has been explicitly
set for these corner cases.
—Rasmus
--
Hvor meget poesi tror De kommer ud af et glas isvand?
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Consider the following example:
>>
>> * h1
>> foo[fn:1]
>>
>> * Footnotes
>> [fn:1] if \alpha $\beta$ \(\gamma\)
>>
>> Narrow it to h1 and export the buffer. Something l
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Narrow to h1 in the following example and run org-footnote-action on the
>> footnote-reference. Expected behavior is IMO to go to the definition.
>> This does not happen.
>
> I disagree. Interactiv
oking into next C-& or
org-footnote-action if it's performed from within the [:begin, :end] range
of the footnote-definition...
* h1
foo[fn:1]
* Footnotes
[fn:1] bar
—Rasmus
--
Er du tosset for noge' lårt!
Rasmus writes:
> Rasmus writes:
>
>> * h1
>> foo[fn:1]
>>
>> * Footnotes
>> [fn:1] if \alpha $\beta$ \(\gamma\)
>>
>> Narrow it to h1 and export the buffer. Something like this is exported:
>
> This also does not seem to work correctly w
Rasmus writes:
> * h1
> foo[fn:1]
>
> * Footnotes
> [fn:1] if \alpha $\beta$ \(\gamma\)
>
> Narrow it to h1 and export the buffer. Something like this is exported:
This also does not seem to work correctly when exporting with ox-html.
But there the problem is that th
blocks for
footnotes that are within the buffer view, but not outside. The patch
fixes the above example, but I doubt it's the Right Wayᵀᴹ to fix this
(i.e. there could be a more fundamental bug).
—Rasmus
--
Bang bang
>From ce22e0e6d92b79cfec41c1a2295f8e0a21cc3775 Mon Sep 17 00:00:00 2001
From:
miss some of them.
>
>> If we add such a variable where should it live? org.el or ox-latex.el?
>
> ox-latex.el. This is a hack. There's no need to leak it elsewhere.
Here's an updated patch.
—Rasmus
--
Need more coffee. . .
>From 5442c61a0ab793d0a0cb3507d4355a5d1fb
ystem the spaces are displayed in the browser. Org-mode version
8.3beta (release_8.3beta-1065-g99609a @ /usr/share/emacs/site-lisp/org/)
Produced code from emacs -q:
In a verse,
indentation should be
preserved.
BTW: Is there a reason why org-html-close-tag inserts an extra space at
the closing
Vicente Vera writes:
> The patch works. Thank you.
Pushed.
--
What will be next?
ith the following example from
emacs -q.
—Rasmus
* set up :noexport:
#+BEGIN_SRC emacs-lisp
(require 'ox-odt)
(setq org-latex-to-mathml-convert-command
"latexmlmath \"%i\" --presentationmathml
sc{is}. It won't manage e.g. (i).
For html you need to add support for a small-caps class.
(defun rasmus/org-guess-textsc (content backend info)
"Automatically downcase and wrap all-caps words in textsc.
The function is a bit slow...
TODO: Make the function work with headlines, but
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Can we have conditional dependence on texmathp?
>
> I guess it doesn't hurt. You need to declare it as an external function
> in order to silence byte-compiler, tho.
You are right. Thanks.
>> If so, maybe somethi
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Nicolas Goaziou writes:
>>
>>> However, "tab:orgtable1" or "sec:orgheadline1" are fine, IMO, since
>>> "org" part can keep the label out of userland.
>>
>> That'
e a macro would be better?
> How would one do that ?
See e.g. org-latex-export-snippet.
> I can't figure out much doc or matching sources to check for hints.
They are called export-snippets.
Hope it helps,
Rasmus
--
It was you, Jezebel, it was you
Hi,
Rasmus writes:
> I still don't know how to reproduce the error. I have tried with Emacs
> 24.4 and the git version.
Sorry for the noise. This should be fixed now.
Thanks,
Rasmus
--
I feel emotional landscapes they puzzle me
Nicolas Goaziou writes:
> However, "tab:orgtable1" or "sec:orgheadline1" are fine, IMO, since
> "org" part can keep the label out of userland.
That's fine with me as well.
—Rasmus
--
Evidence suggests Snowden used a powerful tool called monospaced fonts
Nicolas Goaziou writes:
> Rasmus writes:
>
>> So we could replace ^org with a mapping, e.g. "headline" → "sec:" and
>> "table" → "tab:". Then there's the added safety of TYPE-NUMBER and the
>> expected prefix.
>
> Do y
Nicolas Goaziou writes:
> Rasmus writes:
>
>> That's what I meant. Or rather a wrapper like org-latex--label. A
>> mapping like the one that was reverted for ox-latex only. Or are there
>> pitfalls in that approach?
>
> It will not give you predictability e
).
What is completing-read-function?
Thanks,
Rasmus
--
You people at the NSA are becoming my new best friends!
801 - 900 of 2037 matches
Mail list logo
