Compiling this score (reduced from a larger score) never terminates:
=
\version "2.15.30"
\score
{
\new Staff \relative c'
{
R1 |
\stopStaff
R1 | r2
}
}
=
If I'm stopping the staff I should probably be using spacer rests
instead and this problem g
lilyp...@googlecode.com writes:
> Comment #31 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
> http://code.google.com/p/lilypond/issues/detail?id=2335
>
> Adding empty lines does not help (I tried it almost immediately at the
> beginning, even before reporting the issue).
>
> Just i
Updates:
Labels: -Patch-countdown Patch-push
Comment #14 on issue 2219 by colinpkc...@gmail.com: Set makeinfo and
texi2html error limit to zero
http://code.google.com/p/lilypond/issues/detail?id=2219
Counted down to 20120219, please push
Updates:
Labels: -Patch-countdown Patch-push
Comment #3 on issue 2326 by colinpkc...@gmail.com: Patch: Doc: NR 4.1.4:
document improved spacing on the last page (issue 1377)
http://code.google.com/p/lilypond/issues/detail?id=2326
Counted down to 20120219, please push
Comment #5 on issue 2246 by carl.d.s...@gmail.com: beaming in 3/4 - a
setting to not beam 3 eights against the beat.
http://code.google.com/p/lilypond/issues/detail?id=2246
They are really specific to 3/4 beaming only. 3/4 has special standards
that don't apply to other music. beamHalfMea
Updates:
Labels: -Type-Critical Type-Crash
Comment #34 on issue 2335 by philehol...@gmail.com: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Keeps head down...
The reason I didn't mark this as a critical regression is that I spent some
time looki
Comment #33 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Ok. I'll maybe try to touch it next weekend, but I cannot promise anything
now.
___
bug-lilypond mailing list
bug-li
Comment #32 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Graham, would it be possible to build LilyPond in the same way as
provided binaries are built, but w/o stripping debug symbols?
No. Or rather: it is ce
Comment #31 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Adding empty lines does not help (I tried it almost immediately at the
beginning, even before reporting the issue).
Just in case someone overlooked it, I repeat w
Comment #30 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
valgrind reports a ton of memory invalid reads... but it also reports a ton
of jumps depending on uninitialized variables. I mean, not just running
val
Updates:
Labels: -Patch-review Patch-new
Comment #58 on issue 2148 by mts...@gmail.com: vertical skylines should use
stencil integrals
http://code.google.com/p/lilypond/issues/detail?id=2148
Gets vertical skylines from grob stencils
http://codereview.appspot.com/5626052
___
Comment #29 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
#(gc) does not add music events in a music list. So unless it is an input
alignment problem (does adding empty lines change anything?), this is a
rather sure pointer
Comment #28 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Beside the line mentioned by Graham (damn, I overlooked it), \unfoldRepeats
can be removed too.
David, the problem is that changing this file in almost any way ma
Comment #4 on issue 2246 by x.sche...@gmail.com: beaming in 3/4 - a setting
to not beam 3 eights against the beat.
http://code.google.com/p/lilypond/issues/detail?id=2246
Hi Carl,
What would happen if we set beamHalfMeasure to true in measure that
cannot (hardly) be divided in half? Like
Comment #27 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
It's likely that if you crank some knob concerning garbage collection that
things will be totally different. Unfortunately I see no such knob. Try
putting some #(gc)
Comment #26 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Mike: the bug reporter claimed that he had a tiny example. I called him on
it; he produced another two versions. His final version still looks
large-i
Comment #25 on issue 2335 by mts...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
This is what I meant. I can make LilyPond segfault w/ many a Scheme hack.
Any function that uses unsmob_spanner, for example, will likely segfault if
a grob is p
Comment #24 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
From Scheme, you can't really do much of hacking smobs and memory
management. It is likely that anything you can do to make the problem
disappear is more related to g
Comment #23 on issue 2335 by mts...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
The articulate script has tons of (cool) hacks, many of which may be doing
funny things w/ smobs and memory management. I'd recommend going into the
script and co
Comment #22 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Sorry for off-topic comment, but I feel I have to add this.
This piece is a fragment of my WIP work (well, lately not in progress at
all) that I named early "Tempt
Comment #21 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Even "useless" lines produce music events. As long as it is not purely in
the grob juggling part that the problem is occuring, that is not all that
spectacular.
__
Comment #20 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I never thought I would say it, but I regret that I was not lying (and the
input works flawlessly in 2.14.2, obviously).
$ /home/przemoc/lilypond/2.14.02/usr/bin/
Comment #19 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
holy mao. I owe you an apology, przemoc.
I have verified that commenting out "useless" lines will eliminate the
segfault. strange-bug-strip-3.ly segfau
Comment #18 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
It segfaults on my machine too, so don't feel that it's you personally
guilty (unless you were lying about it working on 2.14.2). I'm not going
to chec
Comment #17 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I am afraid that particularly with a stable release, people tend to use the
provided binaries.
I hate this cross compilation multiplatform business.
Comment #16 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
As it happens extremely rare, only on Linux 64-bit and only on provided
builds, maybe it doesn't need to be marked as critical? I mean, it could
needlessly delay
Comment #15 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Nope.
$ lilypond -ddebug-gc ./strange-bug-strip-3.ly
GNU LilyPond 2.15.30
Processing `./strange-bug-strip-3.ly'
Parsing...
Interpreting music... [8][16]Segmentation
Comment #14 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I missed ties and slurs, they can be removed, but beside that, yes, almost
anything (I may missed something) changed here make segfault gone (and
definitely remov
Comment #13 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Any differences in behavior or output with -ddebug-gc ?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.
Comment #12 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
... seriously? You absolutely *must* have the \time signature? Remove a
single tie ~ will make it work? Removing the left or right hand will make
it
Comment #11 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Here is possibly the limit of my squeezing. Removing _any_ non empty line
here makes segfault disappear. Heck, change first 'dis' to 'd' and it
works. Magic!
At
Comment #10 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I understand you, but it may be a bug that just doesn't manifest when the
code is short. I'll try to simplify it as much as I can preserving the
segfault.
Comment #9 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
@comment 4: guidelines for making a Tiny example are here:
http://lilypond.org/tiny-examples.html
if you can't be bothered to follow them, then I can't be b
Comment #8 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
As stated in the mails and in this issue description, problem regards Linux
64-bit builds linked from LilyPond site. My own build doesn't segfault.
__
Comment #7 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
That's basically useless: looks like you have binaries without debug
symbols. Do have a way to compile the code yourself? If that were
possible, one could at least tr
Comment #6 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
My bad, there is some backtrace available after all:
#0 0x00618a31 in ?? ()
#1 0x0049321d in ?? ()
#2 0x0048b977 in ?? ()
#3 0x00
Comment #5 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
David, my first mail had result from gdb, but it's useless:
Program received signal SIGSEGV, Segmentation fault.
0x00618a31 in ?? ()
I provided ltrace dump:
h
Comment #4 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I would simplify it if I knew how to do it preserving the segfault. :)
Summary of tests performed using 64-bit LilyPonds in Debian Wheezy x64 (as
it should be here
Comment #3 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Can you crash it in the debugger? If that does not work, can you switch on
core dumps (ulimit -c unlimited) and then use the debugger to give a
backtrace?
_
Comment #2 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
woah, that ly is huge! I would have rejected it for not having a Tiny
example.
Could you reduce that to a Tiny example? I particular want to know about
Updates:
Labels: -Type-Crash Type-Critical
Comment #1 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
according to his information about the history, this did not crash in
2.14.2.
___
2012/2/19 Przemysław Pawełczyk :
> On Sun, Feb 19, 2012 at 17:20, Jay Anderson wrote:
>> On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes wrote:
>>> I don't normally install LilyPond on my Linux box - I simply run a
>>> self-compiled version. It's 64-bit Ubuntu and on this, your file compiles
>>> an
"Przemysław Pawełczyk" wrote in message
news:cam3cw+bxphdwzz4enkt9qfopk-82+7dlfx0cpa97fzy1tjx...@mail.gmail.com...
I've digged my VM image of Ubuntu 9.04 64-bit in VirtualBox, installed
64-bit LilyPond 2.15.30 and the segfault is there. So it's definitely
not a Debian-specific issue.
Added a
Status: Accepted
Owner:
Labels: Type-Crash OpSys-Linux
New issue 2335 by philehol...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Reported by Przemysław 'Przemoc' Pawełczyk
With the attached LilyPond source, lilypond downloaded 64 bit binarie
Updates:
Labels: Patch-new
Comment #3 on issue 2246 by carl.d.s...@gmail.com: beaming in 3/4 - a
setting to not beam 3 eights against the beat.
http://code.google.com/p/lilypond/issues/detail?id=2246
I've created two new context properties that specify rules for 3/4 beaming:
beamWhol
On Sun, Feb 19, 2012 at 17:20, Jay Anderson wrote:
> On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes wrote:
>> I don't normally install LilyPond on my Linux box - I simply run a
>> self-compiled version. It's 64-bit Ubuntu and on this, your file compiles
>> and runs fine. So I'm assuming (if you k
On Sun, Feb 19, 2012 at 16:32, Phil Holmes wrote:
> - Original Message - From: "Przemysław Pawełczyk"
>
> To: "Colin Hall"
> Cc: "Phil Holmes" ;
> Sent: Sunday, February 19, 2012 2:51 PM
> Subject: Re: Abrupt end of interpreting music (segmentation fault)
>
>
>
> Thank you, Colin, for C
On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes wrote:
> I don't normally install LilyPond on my Linux box - I simply run a
> self-compiled version. It's 64-bit Ubuntu and on this, your file compiles
> and runs fine. So I'm assuming (if you know better, please say) that this
> is unlikely to be gen
- Original Message -
From: "Przemysław Pawełczyk"
To: "Colin Hall"
Cc: "Phil Holmes" ;
Sent: Sunday, February 19, 2012 2:51 PM
Subject: Re: Abrupt end of interpreting music (segmentation fault)
Thank you, Colin, for CC-ing me.
2012/2/19 Colin Hall :
On Sun, Feb 19, 2012 at 10:45:32
Thank you, Colin, for CC-ing me.
2012/2/19 Colin Hall :
> On Sun, Feb 19, 2012 at 10:45:32AM -, Phil Holmes wrote:
>> >Przemoc's example is not very long, but it involves lots of features.
>> >It would be good for anyone using a 64 bit system to try to reproduce
>> >the segfault (emergency ear
Comment #8 on issue 1833 by reinhold...@gmail.com: Deprecate \fermataMarkup
for full-bar rests.
http://code.google.com/p/lilypond/issues/detail?id=1833
What happened to this patch? I didn't see any objections, most comments in
the codreview are about how to handle depretacted commands in ge
Comment #5 on issue 2333 by reinhold...@gmail.com: extract-texi-filenames
doesn't ignore comments
http://code.google.com/p/lilypond/issues/detail?id=2333
The purpose of this patch is to prevent some warnings about missing include
files while building the documentation (in particular the tra
Updates:
Status: Fixed
Labels: -Patch-review Fixed_2_15_31
Comment #7 on issue 2332 by d...@gnu.org: Patch: make-engraver helper macro
http://code.google.com/p/lilypond/issues/detail?id=2332
Since this is strictly upwards-compatible and passed the checks, pushed as
6ec4177a4076
Comment #5 on issue 1902 by d...@gnu.org: scheme engravers cause "warning:
Attempting to remove nonexisting listener."
http://code.google.com/p/lilypond/issues/detail?id=1902
Strike the whitespace error (there is actually an embarrassing number of
them in parser.yy): the complaint occured d
Updates:
Labels: Patch-review
Comment #4 on issue 1902 by d...@gnu.org: scheme engravers cause "warning:
Attempting to remove nonexisting listener."
http://code.google.com/p/lilypond/issues/detail?id=1902#c4
Patchy the autobot says: LGTM. One whitespace error. Will be fixed
silent
Updates:
Labels: Patch-review
Comment #57 on issue 2148 by d...@gnu.org: vertical skylines should use
stencil integrals
http://code.google.com/p/lilypond/issues/detail?id=2148#c57
Patchy the autobot says: LGTM. Gazillion changes, most of them looking
good. stencil-color-rotation i
wrote in message
news:1-9567054385019064696-15586498251529865272-lilypond=googlecode@googlecode.com...
Updates:
Labels: Patch-new
Comment #1 on issue 2333 by reinhold...@gmail.com: extract-texi-filenames
doesn't ignore comments
http://code.google.com/p/lilypond/issues/detail?id=2333
Fix
Comment #4 on issue 2333 by d...@gnu.org: extract-texi-filenames doesn't
ignore comments
http://code.google.com/p/lilypond/issues/detail?id=2333
Well, I did not mean "regtests" as much as "make check". But of
course "make check" does not involve "make doc": I confused this with the
opera
On Sun, Feb 19, 2012 at 10:45:32AM -, Phil Holmes wrote:
> >Przemoc's example is not very long, but it involves lots of features.
> >It would be good for anyone using a 64 bit system to try to reproduce
> >the segfault (emergency early-stopping of LilyPond) and even better
> >to start reducing
Comment #3 on issue 2333 by philehol...@gmail.com: extract-texi-filenames
doesn't ignore comments
http://code.google.com/p/lilypond/issues/detail?id=2333
I see no reason why it should affect regtests - simply the text sent to
terminal with a make doc.
"Keith OHara" wrote in message
news:loom.20120219t110258-...@post.gmane.org...
Przemysław Pawełczyk gmail.com> writes:
I've provided some more information at:
http://paste.przemoc.net/lilypond/abrupt-end-of-interpreting-music/
GNU LilyPond 2.15.27 - segfault
GNU LilyPond 2.15.28 - ok
GNU L
Comment #3 on issue 1902 by d...@gnu.org: scheme engravers cause "warning:
Attempting to remove nonexisting listener."
http://code.google.com/p/lilypond/issues/detail?id=1902#c3
Issue 1902: scheme engravers cause "warning: Attempting to remove
nonexisting listener."
Implements listener eq
Comment #6 on issue 2332 by d...@gnu.org: Patch: make-engraver helper macro
http://code.google.com/p/lilypond/issues/detail?id=2332
Regarding comment #2: I tackled issue 1902 to stop the complaints. As a
side-effect, you should be able to remove them now in the same manner that
you consiste
Updates:
Status: Verified
Comment #15 on issue 2165 by colingh...@gmail.com: Patch: Modifies broken
hairpin height
http://code.google.com/p/lilypond/issues/detail?id=2165
Verified that this patch was committed to the repo under the committish in
Comment 11 above.
Comment #56 on issue 2148 by d...@gnu.org: vertical skylines should use
stencil integrals
http://code.google.com/p/lilypond/issues/detail?id=2148
Ugh, I tested the previous version. It compiled modulo the three
whitespace errors. One thing might be that a bit of spring/padding around
te
Updates:
Status: Verified
Comment #33 on issue 2171 by colingh...@gmail.com: Patch: Implements DOM-id
property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
Verified that this patch was committed to the repository under the
committish given in Comment 29 above.
Updates:
Status: Verified
Comment #11 on issue 2183 by colingh...@gmail.com: Patch: hideNotes should
also hide rests...
http://code.google.com/p/lilypond/issues/detail?id=2183
Verified that this patch was committed to the repository.
___
b
Updates:
Status: Verified
Comment #11 on issue 2286 by colingh...@gmail.com: Patch: Make #{ c' #} and
x=c' create a pitch instead of a NoteEvent
http://code.google.com/p/lilypond/issues/detail?id=2286
Verified that this patch has been committed to the git repository.
__
Updates:
Status: Verified
Comment #7 on issue 2296 by colingh...@gmail.com: Patch: Stops woodwind
diagram info appearing on terminal
http://code.google.com/p/lilypond/issues/detail?id=2296
Verified that the commit for this patch is in the git repository.
Przemysław Pawełczyk gmail.com> writes:
> I've provided some more information at:
> http://paste.przemoc.net/lilypond/abrupt-end-of-interpreting-music/
> GNU LilyPond 2.15.27 - segfault
> GNU LilyPond 2.15.28 - ok
> GNU LilyPond 2.15.29 - ok
> GNU LilyPond 2.15.30 - segfault
> BTW I'm using 64
Updates:
Status: Verified
Comment #9 on issue 2299 by colingh...@gmail.com: Patch: Adds stencil
command suppressions to changes
http://code.google.com/p/lilypond/issues/detail?id=2299
Verified committish for the patch is in the repo.
___
b
Updates:
Status: Verified
Comment #18 on issue 2300 by colingh...@gmail.com: Patch: do not tinker
with the position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2300
Forgot to change status to Verified.
___
bug-lily
lilypond-4 wrote:
>
>
> Comment #10 on issue 803 by julien.r...@gmail.com: correction needed for
> the German translation of convert-ly
> http://code.google.com/p/lilypond/issues/detail?id=803
>
> I guess we need some input file that contains a \put-adjacent command,
> from
> a version pri
Comment #17 on issue 2300 by colingh...@gmail.com: Patch: do not tinker
with the position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2300
Verified committish for this patch is present in the repository.
___
bug-lilypond m
Updates:
Status: Verified
Comment #9 on issue 2303 by colingh...@gmail.com: Patch: Let EventChord
replay articulations
http://code.google.com/p/lilypond/issues/detail?id=2303
Verified committish is present in the repository.
___
bug-lilypo
Updates:
Status: Verified
Comment #9 on issue 2301 by colingh...@gmail.com: Patch: Fixes cross stem
glissandi
http://code.google.com/p/lilypond/issues/detail?id=2301
Verified that the committish is present in the repository.
___
bug-lilypo
Comment #10 on issue 2301 by colingh...@gmail.com: Patch: Fixes cross stem
glissandi
http://code.google.com/p/lilypond/issues/detail?id=2301
Verified that the committish is present in the repository.
___
bug-lilypond mailing list
bug-lilypond@gnu.
Updates:
Status: Verified
Comment #14 on issue 2311 by colingh...@gmail.com: Patch: Final redirection
of texi output
http://code.google.com/p/lilypond/issues/detail?id=2311
Verified that the committish for this Patch is present in the repository.
I was a bit concerned by the "Not sur
Comment #55 on issue 2148 by mts...@gmail.com: vertical skylines should use
stencil integrals
http://code.google.com/p/lilypond/issues/detail?id=2148#c55
Gets vertical skylines from grob stencils
http://codereview.appspot.com/5626052
___
bug-lily
Updates:
Labels: Patch-review
Comment #2 on issue 2333 by d...@gnu.org: extract-texi-filenames doesn't
ignore comments
http://code.google.com/p/lilypond/issues/detail?id=2333#c2
Patchy the autobot says: LGTM. Was this expected to _not_ change
regtests? Should this be tested once a
Updates:
Status: Verified
Comment #11 on issue 2304 by colingh...@gmail.com: Patch: Fix barre snippet.
http://code.google.com/p/lilypond/issues/detail?id=2304
Verified that the committish for this patch is present in the git
repository.
__
Updates:
Owner: d...@gnu.org
Comment #2 on issue 1902 by d...@gnu.org: scheme engravers cause "warning:
Attempting to remove nonexisting listener."
http://code.google.com/p/lilypond/issues/detail?id=1902
(No comment was entered for this change.)
_
Updates:
Labels: Patch-new
Comment #1 on issue 1902 by d...@gnu.org: scheme engravers cause "warning:
Attempting to remove nonexisting listener."
http://code.google.com/p/lilypond/issues/detail?id=1902#c1
Issue 1902: scheme engravers cause "warning: Attempting to remove
nonexisting
Hi Eluze and Phil,
I did not get your responses. maybe you forgot that
> P.S. Please add me to CC as I'm not on the list.
>> If I run this from the Windows command line, it compiles without problem.
>> Do you think it might have anything to do with articulate? The other
>> strange thing is the b
84 matches
Mail list logo
