not to disturb git bisect.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
version of dev/staging.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
m...@apollinemike.com m...@apollinemike.com writes:
On Oct 28, 2011, at 3:18 PM, David Kastrup wrote:
m...@apollinemike.com m...@apollinemike.com writes:
Sorry for the oversight. Wouldn't it just be easier to commit a new
commit with the change in version number?
Sure, that's certainly
= \tweak #'font-size #-3 -\flageolet
There might be some place where one might use this example in its fixed
form, but as a cover story for the need of inline Scheme code, it is a
complete failure.
--
David Kastrup
___
bug-lilypond mailing list
bug
be related...)
Any help would be appreciated!
Arno
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
want to rebase into
staging). Instead you need to delete and rewrite dev/staging. Deleting
it is done by doing the same push command, just without HEAD before
the colon.
But before you _rewrite_ dev/staging, better ask again.
--
David Kastrup
or deleting this file or other sideeffects or
temporaries without listing them explicitly, make sees no reason not to
run the actions of several rules in parallel.
And it would seem that it ran one rule that removed out/contributor.texi
at an unexpected point of time.
--
David Kastrup
Julien Rioux jri...@physics.utoronto.ca writes:
On 02/11/2011 4:04 PM, David Kastrup wrote:
Julien Riouxjri...@physics.utoronto.ca writes:
On 27/10/2011 7:01 AM, Thomas Spuhler wrote:
LANG= makeinfo --enable-encoding -I
/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.15.15/Documentation
already been _analyzed_ on the
list.
How do you get nondeterminism without parallel jobs? Difficult. It is
possible to write Make rules that fail in progressing places. But
nondeterministically, so that one person sees the failures, and the next
doesn't?
--
David Kastrup
the scheme
files that use the define-markup-command,
(especially define-markup-commands.scm).
Will this affect user-defined markup commands in the document as well?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
recognized when _staging_ was strictly _behind_ master,
and let it catch up, and give _master_ the checking that it never got
(so that we know when to give somebody a kick somewhere), but that is a
different task.
--
David Kastrup
___
bug-lilypond mailing
accidentally click
at the wrong moment when the $#@!%$#% issue list hauls a giant
mouse-over window over your browser window.
Mike probably did not even realize he has hijacked your issue while
sneezing.
--
David Kastrup
___
bug-lilypond mailing list
bug
a choice that's more natural
for musicians, not for programmers.
Unfortunately, it is just programmers and not musicians who have a
reasonable chance of being able to figure out how to produce ♯ on a
computer keyboard.
--
David Kastrup
___
bug
Hans Aberg haber...@telia.com writes:
On 12 Nov 2011, at 05:38, David Kastrup wrote:
Unfortunately, it is just programmers and not musicians who have a
reasonable chance of being able to figure out how to produce ♯ on a
computer keyboard.
One approach is having an editor which can provide
worked, then run convert-ly.
Don't worry that the result looks too easy to be true. Just try it.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
correctly previously, and now #padright
does the same.
Basically, the rule of thumb now is: if you would not have used $
outside of #{ ... #}, don't use it inside.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
, the NR has had its examples converted
in this manner as well).
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
David Kastrup d...@gnu.org writes:
pls p.l.schm...@gmx.de writes:
Hey all,
I tried to compile the following two snippets from the NR:
That's not the current NR, and you are trying the example with a current
Lilypond.
Old files with appropriate \version string will get converted
not interested in discussing any optimal solution at the
moment.
We can revisit this in GOP in 2012.
I would have just kept it at at Patch-new until the block was gone.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
Graham Percival gra...@percival-music.ca writes:
On Tue, Nov 15, 2011 at 11:24:28PM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Patch-waiting: Patch is blocked, but still needs review
I would have just kept it at at Patch-new until the block was gone
structure (in particular an eq?-hashtable or its C++
equivalent) that might involve memory addresses in its hash generation.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
be done before midnight.
No need to panic. It's not like review or countdown of this one have
even started. And I'm also keeping the queues busy with stuff not
needing a version change, too.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond
Thomas tho...@btspuhler.com writes:
rpm installation gives this warnings.
Yes they are warnings, but if someone is picky then they submit bug
reports and I am the maintainer
I hope you get more complete bug reports than that.
--
David Kastrup
as a lookahead token _before_ doing the
assignment to indent. It was shere luck that your indent assignment was
executed _after_ set-paper-size.
Now #, while being read by the lexer, is actually being executed in the
parser at a sane point of time.
--
David Kastrup
want to consider contributing a few
regression tests capturing the essence of your usage patterns.
That way you'd have to fear fewer disruptions to your existing scores in
future.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
Valentin Villenave valen...@villenave.net writes:
On Mon, Nov 21, 2011 at 7:39 PM, David Kastrup d...@gnu.org wrote:
A bug that made it through the reviews, nothing inherently bad about
the design. Thanks for the test example, by the way.
Yes, it looks probably a bit far-fetched but said
David Kastrup d...@gnu.org writes:
Valentin Villenave valen...@villenave.net writes:
On Mon, Nov 21, 2011 at 7:39 PM, David Kastrup d...@gnu.org wrote:
A bug that made it through the reviews, nothing inherently bad about
the design. Thanks for the test example, by the way.
Yes, it looks
as I can tell you could not do before. But
it's not a third as scary to try.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
the `unspecified'
value.
So if they want people to have a reasonably working upgrade path from
1.8, they better make sure that 1.8 documents the things they want to
be seeing in code.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond
David Kastrup d...@gnu.org writes:
Ian Hulin i...@hulin.org.uk writes:
This is forwarded from the Guile bug list. Bug-squad please create a
LilyPond issue for this - we need to change our code:
Files affected appear (according to git grep) to be:
lily/mensural-ligature.cc
lily/system.cc
David Kastrup d...@gnu.org writes:
Ian Hulin i...@hulin.org.uk writes:
This is forwarded from the Guile bug list. Bug-squad please create a
LilyPond issue for this - we need to change our code:
Files affected appear (according to git grep) to be:
lily/mensural-ligature.cc
lily/system.cc
David Kastrup d...@gnu.org writes:
Ian Hulin i...@hulin.org.uk writes:
This is forwarded from the Guile bug list. Bug-squad please create a
LilyPond issue for this - we need to change our code:
Files affected appear (according to git grep) to be:
lily/mensural-ligature.cc
lily/system.cc
this does not seem like an iron-clad rule.
Unfortunately, I can't think of a good workaround, but I figured I'd
raise that issue.
Well, hmph. I'd want to avoid introducing a differently-named command
for also specifying the context to use.
--
David Kastrup
Carl Sorensen c_soren...@byu.edu writes:
On 11/21/11 1:35 PM, David Kastrup d...@gnu.org wrote:
I don't throw out functionality as a rule. ly:export was an exception
to that rule because its presence was fundamentally incompatible with
maintaining predictable timing for #. But I backed up
Valentin Villenave valen...@villenave.net writes:
On Mon, Nov 21, 2011 at 7:39 PM, David Kastrup d...@gnu.org wrote:
While the above example works fine now, when
using ly:parser-include-string, it is preferable to use $ to avoid
having your string getting injected _asynchronously_ after
. As far as I know, Windows has no
PDF print driver out of the box.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
on Savannah
Hm. Should we really verify already when the commit made it to
staging? That makes the state rather arbitrary. I'd wait at least
until it has migrated properly to master (since that's when it has
received its principal verification and blessing).
Graham? Any opinion on that?
--
David
Graham Percival gra...@percival-music.ca writes:
On Mon, Nov 28, 2011 at 10:54:31AM +0100, David Kastrup wrote:
Hm. Should we really verify already when the commit made it to
staging?
Yes. Brief discussion was 1-3 weeks ago.
That makes the state rather arbitrary. I'd wait at least
updated your file using
convert-ly -ed
on the last working version of that file (with a \version string
corresponding to a version that worked before the change) instead of
manually changing the \version string, the changes would have been made
automatically for you.
--
David Kastrup
Pierre Perol-Schneider pierre.schneider.pa...@gmail.com writes:
2011/11/28 David Kastrup d...@gnu.org
Pierre Perol-Schneider pierre.schneider.pa...@gmail.com writes:
[...]
The syntax has changed in 2.15.10. If you had updated your file using
convert-ly -ed
on the last working version
Graham Percival gra...@percival-music.ca writes:
On Mon, Nov 28, 2011 at 11:16:55AM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Too hard for people with less than 5 hours of training to
determine.
I am not sure I understand that rationale.
git log
Colin Campbell c...@shaw.ca writes:
On 11-11-28 11:39 AM, Phil Holmes wrote:
David Kastrup d...@gnu.org wrote in message
news:87r50syvzn@fencepost.gnu.org...
Actually, the verification for a commit id to be in master can be as
simple as
git fetch
git log origin
Valentin Villenave valen...@villenave.net writes:
On Fri, Nov 25, 2011 at 6:18 PM, David Kastrup d...@gnu.org wrote:
Valentin, any more news of bad effects on your scores? Apart from the
bug that should now be fixed?
OK, I've now had a chance to test the staging code, it's certainly
without change, there is no real
option except keeping old versions of Lilypond around.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Valentin Villenave valen...@villenave.net writes:
On Fri, Dec 2, 2011 at 1:05 AM, David Kastrup d...@gnu.org wrote:
The reason is that eval-string in Guile does not set
port-line/port-filename to sensible values and I use them for making
sensible error messages actually pointing to the source
Valentin Villenave valen...@villenave.net writes:
On Fri, Dec 2, 2011 at 10:14 AM, David Kastrup d...@gnu.org wrote:
Upgrade, rinse and repeat. Up to now, your problems have exclusively
been unrelated to the nature of the patches, but rather because of
bugs slipping through the current
correctness.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
the implementation of
vectors depend on special syntax unnecessarily.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
properly.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Valentin Villenave valen...@villenave.net writes:
On Fri, Dec 2, 2011 at 1:59 PM, David Kastrup d...@gnu.org wrote:
I don't see why defmacro should have ceased working, so it might be
worth revisiting the problems you experienced.
It's not defmacro that ceased working, it's just that I
David Kastrup d...@gnu.org writes:
Valentin Villenave valen...@villenave.net writes:
myvar = { b'4 }
$(display this shouldn't be needed anyway)
$(eval-string (define-public myvar #{ a'2 #} ) )
\new Staff \myvar
You need #(display ...). $ takes a look at the type of the enclosed
) from more complex Scheme structures. But
some-scheme-construct can't go looking for arguments in Lilypond syntax.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Valentin Villenave valen...@villenave.net writes:
On Sun, Dec 4, 2011 at 9:38 AM, David Kastrup d...@gnu.org wrote:
Apart from the rest of this ugly contraption,
You mean, uglier than using eval-string? I'm not sure what a less ugly
way of doing that would look like. (Perhaps using hooks
Valentin Villenave valen...@villenave.net writes:
On Sun, Dec 4, 2011 at 1:20 PM, David Kastrup d...@gnu.org wrote:
You can use `$' with a Scheme expression anywhere you could use
`\NAME' after having assigned the Scheme expression to a variable NAME.
This replacement happens in the `Lexer
is to place the
documentation within the object, or rather whether the desire is to
register object _name_ and documentation somewhere where the
documentation printer can sort and arrange it for generating the
manuals.
--
David Kastrup
___
bug-lilypond
Valentin Villenave valen...@villenave.net writes:
On Fri, Dec 2, 2011 at 1:59 PM, David Kastrup d...@gnu.org wrote:
I don't see why defmacro should have ceased working, so it might be
worth revisiting the problems you experienced.
It's not defmacro that ceased working, it's just that I
Valentin Villenave valen...@villenave.net writes:
On Sun, Dec 4, 2011 at 5:06 PM, David Kastrup d...@gnu.org wrote:
`(module-define! (current-module) (string-symbol ,token)
Wow, interesting. I had seen such things in Nicolas' code (and in
LilyPond codebase), but couldn't understand what
machines might shrug memory leaks off,
but for something like running large builds or regtests, it is not funny
when the memory requirements keep growing during a multi-source run.
Not to mention that this stuff can also cause crashes and Heisenbugs.
--
David Kastrup
'_\espressivo1
e'!_\espressivo1
eis'_\espressivo1
ees'_\fermata1
e'!_\fermata1
eis'_\fermata1
}
inline: script-accidental-collision.png
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug
page...
Drawing systems...
Layout output to `test.ps'...
Converting to `./test.pdf'...
Success: compilation successfully completed
Compilation finished at Wed Dec 7 11:57:07
I think this should be made to work.
--
David Kastrup
___
bug-lilypond mailing
this problem?
Sure you don't have an executable or even a dead symbolic link in
/home/nick/lilypond or /home/nick/bin or so?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Nick Payne nick.pa...@internode.on.net writes:
No, I ran find ~/ -name lilypond and nothing was found.
env | grep lilypond
is also empty?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo
of an argument, so -dpoint-and-click=#f would not work,
but -dpoint-and-click=#f would?
It is also conceivable that this depends on the startup stub of whatever
compiler you happened to be using.
I know why I don't do Windows.
--
David Kastrup
___
bug-lilypond
Eluze elu...@gmail.com writes:
David Kastrup dak at gnu.org writes:
It is also conceivable that this depends on the startup stub of whatever
compiler you happened to be using.
I know why I don't do Windows.
anything works:
-dpoint-and-click=#f
-dpoint-and-click=#f
-dpoint-and-click
for the definition and
\violin #(+ 1 2)
for use.
Or
sonata = \vector 2
sonata1 = \struct #'(expo modulation reprise)
sonata1 #'expo = { ... }
sonata1 #'modulation = { ... }
sonata1 #'reprise = { ... }
Something like that.
--
David Kastrup
___
bug
of skills. It is just boring and ugly
grindwork nobody can be interested in.
So you should be careful about relying on q in scores that pass music
through music variables or music functions before applying \relative.
--
David Kastrup
___
bug-lilypond
relative _and_ q. After all, they will only need the
compatibility option when they mess with EventChords themselves or got
hold of code that does and that wants updating anyhow.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
without changing @{ and @}
back.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
in the order, before the clef
engraver runs.
At least there should be an option to suppress such annoying
optimization.
It is not an optimization.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo
, I would just use count? here and save a positive integer or
zero for the documentation string.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
resolve the problem on his own?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
David Kastrup d...@gnu.org writes:
Ian Hulin i...@hulin.org.uk writes:
On 29/12/11 11:13, lilyp...@googlecode.com wrote:
Comment #6 on issue 2149 by m...@apollinemike.com: Patch: Creates
non-negative-integer? predicate.
http://code.google.com/p/lilypond/issues/detail?id=2149
I'll
?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
will you discern intended and unintended input?
How do you use invalid utf-8 sequences as intended input?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
\sarabandeP
\sarabandeBP
\header {
piece =
4. With something in front of the grace note, rendering is OK. }
}
}
--
David Kastrup
___
bug-lilypond mailing list
bug
of several of them
being just right is not all that high.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
really see the point in giving up before trying.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
: If
Pango reports an invalid UTF-8 sequence (as it already does), I'm all
for it to make it more visible. What kind of improvement do you
envision?
UTF-8 is Lilypond's _input_ encoding. There is no point in leaving it
to its backends to complain.
--
David Kastrup
Werner LEMBERG w...@gnu.org writes:
UTF-8 is Lilypond's _input_ encoding. There is no point in leaving
it to its backends to complain.
But string handling is delegated to Pango...
Not as far as I can see. String _typesetting_ is delegated to Pango.
--
David Kastrup
, but I have not diagnosed this in detail. Might be
something else.
Does anybody know whether this discussion reaches him?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
checked-out branch.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
code
from `gnulib', file `unistr/u8-check.c'.
Issue number: 5505090 (http://codereview.appspot.com/5505090)
Issue description:
lexer.ll: Warn about non-UTF-8 characters
Making the warnings point to the exact bad byte rather than the
enclosing construct would be nice.
--
David Kastrup
Phil Holmes m...@philholmes.net writes:
David Kastrup d...@gnu.org wrote in message
news:87ipkwu66v@fencepost.gnu.org...
lilyp...@googlecode.com writes:
Comment #4 on issue 2156 by pkx1...@gmail.com: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
Phil,
I *think
example (of a particularly famous piece), so should
follow the practice of the majority of editions.
It would still make sense to add a comment to that effect.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org
, even if it is
easier to fix than the music.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
://codereview.appspot.com/5505090#msg5
for a reasoning about the current approach for this patch.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hans Aberg haber...@telia.com writes:
On 1 Jan 2012, at 21:06, David Kastrup wrote:
Updates:
Labels: Patch-new
Comment #2 on issue 2159 by d...@gnu.org: Patch: lexer.ll: Warn
about non-UTF-8 characters
http://code.google.com/p/lilypond/issues/detail?id=2159#c2
lexer.ll: Warn about
feeling more enlightened after reading this
paragraph than without it.
You might want to write in a less abstract manner and possibly create an
actual example illustrating what you want to see documented.
--
David Kastrup
___
bug-lilypond mailing list
bug
,
and at this time of year, gets rather vague about days, months, and
even years!
Cheers,
Colin Chastened Campbell
Oh, this was not intended to be a chastening. In fact, I was glad to
have a somewhat plausible excuse for my lack of patience.
--
David Kastrup
to get rid of its energy but just
changes its frequency).
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
articulations of NoteEvents (rhythmic events?) for pitches
as well.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
the CPU can keep busy on processing a second job when the other
job is waiting for the disk to provide new input.
More importantly, you'll get to see the same kind of problems that the
true multi-core people experience when using -j.
So very much recommended for testing.
--
David Kastrup
be different, but stepping on the brakes for your
eye movement like that does not seem healthy to me.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
(in my first example). This simply looks wrong to me.
I do attach an excerpt of my real world example, without
\newSpacingSection.
I'd say that spacing becomes tight too fast here, not that it starts out
too lose.
--
David Kastrup
___
bug-lilypond
reverts should they prove necessary, it is piecemeal work.
Hopefully finished some time today.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
chord. Or when you use music variables with a q in them before any
other chord, and employ those in \relative.
So I don't think that there is much cause for worry.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org
matter since we certainly had a
discussion about that already before the policy went into the CG.
I misremembered, so sorry for the unwarranted change.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman
of what it would check out when doing an
argument-less commit and then checkout.
I have problems guessing the intent of those lines.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
/gperciva/lilypond-extra/blob/master/patches/projecthosting_patches.py#L106
Amusingly, apparently somebody added code to handle the bits, but
not the URL: part.
Both forms are in use, but I thought the URL: form was, stupid as it
looks, more or less considered correct in mails.
--
David
Graham Percival gra...@percival-music.ca writes:
On Sun, Jan 29, 2012 at 06:34:16PM +0100, David Kastrup wrote:
lilyp...@googlecode.com writes:
Amusingly, apparently somebody added code to handle the bits, but
not the URL: part.
Both forms are in use, but I thought the URL: form
201 - 300 of 1473 matches
Mail list logo
