On Sat, Jan 10, 2009 at 07:06:41PM +0100, Pavel Sanda wrote:
Angus Leeming wrote:
We had one curmudgeonly gentleman, John Weiss, who point blank refused to
licence his contribution to LyX under the GPL version 2 or later. The old
flavour of this page has him down as licencing his
On Sat, Jan 10, 2009 at 07:06:41PM +0100, Pavel Sanda wrote:
> Angus Leeming wrote:
> > We had one curmudgeonly gentleman, John Weiss, who point blank refused to
> > licence his contribution to LyX under the GPL version 2 or later. The old
> > flavour of this page has him
anything of mine. But even beforehand, I preferred to
release all of my code and documentation under the Artistic License.
Any contributions I made to LyX (early reLyX, documentation) should
therefore be considered as originally under the Artistic License.
Make of that what you will.
--
John Weiss
L or LGPL anything of mine. But even beforehand, I preferred to
release all of my code and documentation under the Artistic License.
Any contributions I made to LyX (early reLyX, documentation) should
therefore be considered as originally under the Artistic License.
Make of that what you will.
tested with bash, ash, csh, tcsh, ksh, and bsh.)
For Windows, however I wouldn't be surprised if whitespace chars
weren't escaped. Just another one of those platform differences
that'll need special handling.
--
John Weiss
!
Does that help at all, Andreas?
--
John Weiss
On Tue, Jan 25, 2005 at 09:16:38AM +0100, Asger Ottar Alstrup wrote:
John Weiss wrote:
[A great opportunity to have a little flame-fest.]
You're the one attacking me out-of-hand.
Not FUD. Reality. [Long story about something irrelevant.]
Took them YEARS to get it to that state.
Sad
.
In short: calling a function lyxbreaker is a Bad Idea, as it
implies that this function somehow damages LyX. Better to call it
lyxstopper or lyxbreakpt, the latter being far more descriptive if
its purpose.
--
John Weiss
. IMHO of course.)
Seconded.
--
John Weiss
On Tue, Jan 25, 2005 at 09:30:45AM +, Angus Leeming wrote:
John Weiss wrote:
On Fri, Jan 21, 2005 at 09:57:48PM +, Angus Leeming wrote:
Cygwin's POSIX emulation layer avoids
the need for the various workarounds required when using other
compilers under MS-Windows.
See! See
muddy code in a Unix-Windows-crossplatform program will
require a bit of work (in which I include careful planning). Which
was the whole point of those cautioning posts of mine.
--
John Weiss
dissertation and see if I'm even on the right track here, or if my
memory's flakey.)
--
John Weiss
The single-quotes protected the
space from the shell. (I tested with bash, ash, csh, tcsh, ksh, and bsh.)
For Windows, however I wouldn't be surprised if whitespace chars
weren't escaped. Just another one of those platform differences
that'll need special handling.
--
John Weiss
ment: Don't even
THINK of using another type of "fooXYZ" with this code! Putting in a
toplevel "using std::ostream;" tells future authors that no one, no
one at all, should even try to use anything but the STL ostream with
this code... put it in another source file and link the two together
instead!
Does that help at all, Andreas?
--
John Weiss
On Tue, Jan 25, 2005 at 09:16:38AM +0100, Asger Ottar Alstrup wrote:
> John Weiss wrote:
> [A great opportunity to have a little flame-fest.]
You're the one attacking me out-of-hand.
> >Not FUD. Reality. [Long story about something irrelevant.]
> > Took them YEARS to ge
d to "circuit breaker", the thing in your electric panel that
severs an electrical circuit pulling too many amps.
In short: calling a function "lyxbreaker" is a Bad Idea, as it
implies that this function somehow damages LyX. Better to call it
"lyxstopper" or "lyxbreakpt", the latter being far more descriptive if
its purpose.
--
John Weiss
> justified. IMHO of course.)
Seconded.
--
John Weiss
On Tue, Jan 25, 2005 at 09:30:45AM +, Angus Leeming wrote:
> John Weiss wrote:
>
> > On Fri, Jan 21, 2005 at 09:57:48PM +, Angus Leeming wrote:
> >> Cygwin's POSIX emulation layer avoids
> >> the need for the various workarounds required when using other
&
to watch out
> for.
And avoiding muddy code in a Unix-Windows-crossplatform program will
require a bit of work (in which I include careful planning). Which
was the whole point of those cautioning posts of mine.
--
John Weiss
f an figure float
were tunable. (How easy it would be... I'd have to dig out my
dissertation and see if I'm even on the right track here, or if my
memory's flakey.)
--
John Weiss
On Sat, Jan 22, 2005 at 03:30:44PM +0100, Asger Ottar Alstrup wrote:
John Weiss wrote:
Doing true full-Windows support in an inherently-unix program is a
very thorny, messy situation.
Have a look at the patch and then give your comments rather than this FUD.
Not FUD. Reality. Be fair
that are the joy-killer now.
Decidedly mean, IMNSHO.
--
John Weiss
is that Qt provides a handle to do this and that we
use it already.
...which brings me back to my earlier statement: we need to go
through a p.i.-layer, be it our own, or someone else's. ;)
--
John Weiss
.
Have I *finally* made myself clear, Asger? Have I overexplained my
past experiences sufficiently enough that you won't jump all over me?
--
John Weiss
On Sat, Jan 22, 2005 at 09:50:51AM +0100, Andre Poenitz wrote:
On Tue, Jan 18, 2005 at 07:36:36AM -0500, John Weiss wrote:
On Mon, Jan 17, 2005 at 02:09:33PM +0100, Lars Gullik Bjønnes wrote:
I feel we are beginning on a slippery slope now... ok to support
windows if only minimal
might be able to explain what's going
on. (Maybe not, though, as I'm doing this from a laptop on a train.)
--
John Weiss
Asger says I am!
--
John Weiss
On Sat, Jan 22, 2005 at 03:30:44PM +0100, Asger Ottar Alstrup wrote:
> John Weiss wrote:
> >Doing true full-Windows support in an inherently-unix program is a
> >very thorny, messy situation.
>
> Have a look at the patch and then give your comments rather than this FU
d
> | declarations.
>
> :-)
>
> So its you that are the joy-killer now.
Decidedly mean, IMNSHO.
--
John Weiss
tform-independence. ;)
> ...and the good news is that Qt provides a handle to do this and that we
> use it already.
...which brings me back to my earlier statement: we need to go
through a p.i.-layer, be it our own, or someone else's. ;)
--
John Weiss
ossibly) requiring some
deep thought.
Have I *finally* made myself clear, Asger? Have I overexplained my
past experiences sufficiently enough that you won't jump all over me?
--
John Weiss
On Sat, Jan 22, 2005 at 09:50:51AM +0100, Andre Poenitz wrote:
> On Tue, Jan 18, 2005 at 07:36:36AM -0500, John Weiss wrote:
> > On Mon, Jan 17, 2005 at 02:09:33PM +0100, Lars Gullik Bjønnes wrote:
> > >
> > > I feel we are beginning on a slippery slope now... ok to su
what you
mean by "justified paragraph", I might be able to explain what's going
on. (Maybe not, though, as I'm doing this from a laptop on a train.)
--
John Weiss
t his ass like Asger says I am!
--
John Weiss
place. Needed to avoid too much ERT, which is such an
anathema these days. grumble Since most users won't touch it most
of the time, that makes it a *perfect* candidate for the Extended.lyx
manual. [See? See? There *was* a method to my original design
madness! ;)]
--
John Weiss
that you've rederived fire from first
principles. It's a solved problem, and not worth revisiting.
--
John Weiss
to see the payoff? :)
--
John Weiss
gymnastics... I could go on. Suffice it to say that it's enough to
keep a CompSci PhD fully employed at one place I used to work.
Best to keep things simple for now, as Lars says.
--
John Weiss
.
Long Live WYSIWYM!
So, it has its place. Needed to avoid too much ERT, which is such an
anathema these days.Since most users won't touch it most
of the time, that makes it a *perfect* candidate for the Extended.lyx
manual. [See? See? There *was* a method to my original design
madness! ;)]
--
John Weiss
That's like banging two rocks
together and being proud that you've rederived fire from first
principles. It's a solved problem, and not worth revisiting.
--
John Weiss
the 1.4 cycle.
Ain't it great to see the payoff? :)
--
John Weiss
pure Win-libs often requires odd
gymnastics... I could go on. Suffice it to say that it's enough to
keep a CompSci PhD fully employed at one place I used to work.
Best to keep things simple for now, as Lars says.
--
John Weiss
just a library that the
frontend calls into.
A Fine Idea. I approve wholeheartedly.
(Not that you needed my approval. ;) )
--
John Weiss
On Thu, Jan 13, 2005 at 09:05:05AM +0100, Georg Baum wrote:
John Weiss wrote:
1. External LaTeX packages have no place in LyX.
The question was not to include the LaTeX files, but the layout files.
2. What the heck is a beamer?
A very nice and powerful presentation class, and even
On Fri, Jan 14, 2005 at 10:09:29AM +0100, Lars Gullik Bjønnes wrote:
John Weiss [EMAIL PROTECTED] writes:
We (or I) do not want us to require a
lot of ERT to make the printed doc look nice, if ERT is needed then we
are missing features.
That was certainly the case when I last touched
On Thu, Jan 13, 2005 at 03:46:00AM +0100, Uwe Stöhr wrote:
John Weiss wrote:
2. What the heck is a beamer?
Just because you think it's the greatest-thing-since-sliced-bread
doesn't mean everyone else does. Or even knows it exists. (Your bias
is showing, Uwe!)
(Nobody forces you to add
on" is that the core is almost just a library that the
> frontend calls into.
A Fine Idea. I approve wholeheartedly.
(Not that you needed my approval. ;) )
--
John Weiss
On Thu, Jan 13, 2005 at 09:05:05AM +0100, Georg Baum wrote:
> John Weiss wrote:
>
> > 1. External LaTeX packages have no place in LyX.
>
> The question was not to include the LaTeX files, but the layout files.
>
> > 2. What the heck is a beamer?
>
> A very nic
On Fri, Jan 14, 2005 at 10:09:29AM +0100, Lars Gullik Bjønnes wrote:
> John Weiss <[EMAIL PROTECTED]> writes:
>
> We (or I) do not want us to require a
> lot of ERT to make the printed doc look nice, if ERT is needed then we
> are missing features.
That was certainly the cas
On Thu, Jan 13, 2005 at 03:46:00AM +0100, Uwe Stöhr wrote:
> John Weiss wrote:
> >2. What the heck is a beamer?
> >
> >Just because you think it's the greatest-thing-since-sliced-bread
> >doesn't mean everyone else does. Or even knows it exists. (Your bias
> &
On Thu, Jan 13, 2005 at 10:07:27AM +0100, Jean-Marc Lasgouttes wrote:
Uwe == Uwe Stöhr [EMAIL PROTECTED] writes:
Uwe John Weiss wrote:
Doesn't follow a strucutred concept, eh? Maybe you should read the
mailling list archives before insulting me.
Uwe Sorry I wouldn't harm anybody. I
On Thu, Jan 13, 2005 at 10:06:09AM +0100, Lars Gullik Bjønnes wrote:
John Weiss [EMAIL PROTECTED] writes:
| On Fri, Jan 07, 2005 at 05:18:23PM +0100, Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| Given this, which is MacOS X code to fill 'application_support
On Thu, Jan 13, 2005 at 03:34:24AM +0100, Uwe Stöhr wrote:
John Weiss wrote:
Doesn't follow a structured concept, eh?
Maybe you should read the mailling list archives before insulting me.
Sorry I wouldn't harm anybody. I didn't know that there is an active doc
maintainer. I asked
On Wed, Jan 12, 2005 at 05:20:49PM -0800, Jeremy C. Reed wrote:
On Wed, 12 Jan 2005, John Weiss wrote:
Use a separate doc and include it via a master doc.
I was thinking about that. Other than the book will have a lot of
redundant information.
Yes, that is a problem, isn't it?
One
. :)
--
John Weiss
those suggestions that conflict with the design.
Just like Lars has to reject patches that conflict with the code
design.
Fifth, I forget fifth. Vielleicht erinnere ich mich daran spter...
--
John Weiss
On Thu, Jan 13, 2005 at 10:07:27AM +0100, Jean-Marc Lasgouttes wrote:
> >>>>> "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes:
>
> Uwe> John Weiss wrote:
> >> Doesn't follow a strucutred concept, eh? Maybe you should read the
> >>
On Thu, Jan 13, 2005 at 10:06:09AM +0100, Lars Gullik Bjønnes wrote:
> John Weiss <[EMAIL PROTECTED]> writes:
>
> | On Fri, Jan 07, 2005 at 05:18:23PM +0100, Lars Gullik Bjønnes wrote:
> >> Angus Leeming <[EMAIL PROTECTED]> writes:
> >>
> >
On Thu, Jan 13, 2005 at 03:34:24AM +0100, Uwe Stöhr wrote:
> John Weiss wrote:
>
> >Doesn't follow a structured concept, eh?
> >Maybe you should read the mailling list archives before insulting me.
>
> Sorry I wouldn't harm anybody. I didn't know that there is an active d
On Wed, Jan 12, 2005 at 05:20:49PM -0800, Jeremy C. Reed wrote:
> On Wed, 12 Jan 2005, John Weiss wrote:
>
> > Use a separate doc and include it via a master doc.
>
> I was thinking about that. Other than the book will have a lot of
> redundant information.
Yes, tha
ot; and "ey" can have
the same pronounciation, but "ee" and "ay" never do. :)
--
John Weiss
r, docs have a design, too. You'll need to
ignore those suggestions that conflict with the design.
Just like Lars has to reject patches that conflict with the code
design.
Fifth, I forget fifth. Vielleicht erinnere ich mich daran spïter...
--
John Weiss
esoteric features into the Extended doc.
--
John Weiss
.)
--
John Weiss
thought of that, tho. ;)
--
John Weiss
to minimize those by using
manual linebreaks on text that went wonky in print.
--
John Weiss
to you?
Maybe Key thinks Andreas is cute...
Maybe Key is of the opposite sex?
What's that got to do with it?
We're here! We're Queer! And we use LyX! :)
--
John Weiss
ssible mathed features in the User's Guide precisely because of
scope. Better to move the more esoteric features into the Extended doc.
--
John Weiss
e use of a laptop during the trip to/from
Manhattan.)
--
John Weiss
ans train their kids to be cruel.
> Maybe a typo for "Okay, do key" ? Can you say "do key" instead of
> "press key" ?
Also possible. Hand't thought of that, tho. ;)
--
John Weiss
ing text. Though, I tried to minimize those by using
manual linebreaks on text that went wonky in print.
--
John Weiss
press
> > key" ?
> >
> > Why would you "do Key"? What wrong has Key ever done to you?
Maybe Key thinks Andreas is cute...
> Maybe Key is of the opposite sex?
What's that got to do with it?
We're here! We're Queer! And we use LyX! :)
--
John Weiss
...
You are right, I dropped this now.
I think what you want to do instead, Uwe, is to add a chapter to
Customization roughly outlining what all of the different addons are,
by category, and why one might want them.
--
John Weiss
to reference.
It jumps from one label to the next. So the menu name is a bit
confusing. It should better have the name Label.
And this is where your job as doc-editor comes in. ;) Describe
that thang!
--
John Weiss
their paragraph style, then this is indeedy-deed
a bug introduced in v1.4CVS.
--
John Weiss
know.
Hmm... now that I read this, it makes me think that, perhaps, the
details about the different flavors of spellchecker belong in
Customization.lyx
--
John Weiss
: are you overdesigining? Do
we really need this-or-that feature you want to add?
And, in the case of the docs, can you put yourself and your own agenda
(printable book) aside and make decisions grounded in practical,
broad-user-community-consensus-based reasons?
--
John Weiss
. geometry.sty), it'd
already have integrated LyX support. If it's The Future, the devteam
will discover it soon enough...
--
John Weiss
.
Granted, it's not ideal, but it accomplishes what you want, and avoids
the nasty reinterpret_cast()...
--
John Weiss
technique I used 7 years ago. Very good
for such global doc-refactors.)
--
John Weiss
Help-LaTeX
Configuration?
No I mean exactly this one.
In case no one's sent you theirs, I'm attaching the one from the laptop.
--
John Weiss
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass article
\language english
\inputencoding default
... to serve this very purpose.
Ignore online readability/navigability at your peril!
--
John Weiss
what might have sped up the installation...
>
> You are right, I dropped this now.
I think what you want to do instead, Uwe, is to add a chapter to
Customization roughly outlining what all of the different addons are,
by category, and why one might want them.
--
John Weiss
ut it doesn't jump from reference to reference.
> It jumps from one label to the next. So the menu name is a bit
> confusing. It should better have the name "Label".
And this is where your job as doc-editor comes in. ;) Describe
that thang!
--
John Weiss
ction-headings lose their paragraph style, then this is indeedy-deed
a bug introduced in v1.4CVS.
--
John Weiss
l count for
> other spellchecker options. Don't know.
Hmm... now that I read this, it makes me think that, perhaps, the
details about the different flavors of spellchecker belong in
Customization.lyx
--
John Weiss
er audience of LyX users.
As much as we'd all love to have someone, anyone, updating the docs, I
have to play Lars here for a sec and ask: are you overdesigining? Do
we really need this-or-that feature you want to add?
And, in the case of the docs, can you put yourself and your own agenda
re really all that critical (like e.g. geometry.sty), it'd
already have integrated LyX support. If it's The Future, the devteam
will discover it soon enough...
--
John Weiss
for the
1st '\0', then std::string::erase() from that point onward.
Granted, it's not ideal, but it accomplishes what you want, and avoids
the nasty reinterpret_cast<>()...
--
John Weiss
spell'"
again to make sure you got them all.
(This is the very same technique I used 7 years ago. Very good
for such global doc-refactors.)
--
John Weiss
nks.
> >
> >I guess you don't mean the file that you can get via Help->LaTeX
> >Configuration?
>
> No I mean exactly this one.
In case no one's sent you theirs, I'm attaching the one from the laptop.
--
John Weiss
#LyX 1.3 created this file. For more info see h
; special character ... to serve this very purpose.
Ignore online readability/navigability at your peril!
--
John Weiss
Okie-dokie
Ok, dokey is an affirmative reply to someone named, dokey. ;)
--
John Weiss
and call them by
default instead.
--
John Weiss
dokee"
"Okie dokie"
"Okie-dokie"
"Ok, dokey" is an affirmative reply to someone named, "dokey". ;)
--
John Weiss
ot;
exe $CMD `cygpath -aw "$@"`
Easy.
So, for Cygwin, we can just provide these wrappers and call them by
default instead.
--
John Weiss
is GPL.
I want to test a print-on-demand service. I want to submit the LyX
documentation in a single PDF format for a single book. Is this okay?
I belive that would be ok, but you might try to ask John Weiss who is the
main author of the documentation, and as such he would be the main
I believe that a
> fair interpretation of intent is that the documentation is GPL.
>
> > I want to test a print-on-demand service. I want to submit the LyX
> > documentation in a single PDF format for a single book. Is this okay?
>
> I belive that would be ok, but you might try to ask
.
--
John Weiss
for the Win-version
of LyX.
--
John Weiss
1 - 100 of 528 matches
Mail list logo
