On Fri, May 03, 2024 at 02:41:19PM GMT, Jean-Marc Lasgouttes wrote:
> Le 03/05/2024 à 11:56, Jean-Marc Lasgouttes a écrit :
> > I have part of the answer: the slight delay comes from the fact that
> > updateBuffer() is invoked when the selection becomes empty, and since it
> > goes through all docu
Le 03/05/2024 à 11:56, Jean-Marc Lasgouttes a écrit :
I have part of the answer: the slight delay comes from the fact that
updateBuffer() is invoked when the selection becomes empty, and since it
goes through all documents, this takes some time.
Now I have to find out why.
Fixed in master at
Le 22/04/2024 à 20:47, Scott Kostyshak a écrit :
To reproduce:
1. Move the attached file in the lib/docs directory.
2. Open the file.
3. Put the cursor before, e.g., the Additional.lyx include.
4. Press Shift + Down (or Shift + Up).
Result is that there is a small pause before the selection is
l.lyx include.
> > 4. Press Shift + Down (or Shift + Up).
> >
> > Result is that there is a small pause before the selection is finished.
> > Subsequent presses extending the selection in the same direction are almost
> > instantaneous, so it's just the first
efore, e.g., the Additional.lyx include.
> > 4. Press Shift + Down (or Shift + Up).
> >
> > Result is that there is a small pause before the selection is finished.
> > Subsequent presses extending the selection in the same direction are
> > almost instantaneous, so it's
On 4/22/24 14:47, Scott Kostyshak wrote:
To reproduce:
1. Move the attached file in the lib/docs directory.
2. Open the file.
3. Put the cursor before, e.g., the Additional.lyx include.
4. Press Shift + Down (or Shift + Up).
Result is that there is a small pause before the selection is
Am Mon, 22 Apr 2024 14:47:10 -0400
schrieb Scott Kostyshak :
> To reproduce:
>
> 1. Move the attached file in the lib/docs directory.
> 2. Open the file.
> 3. Put the cursor before, e.g., the Additional.lyx include.
> 4. Press Shift + Down (or Shift + Up).
>
> Result
To reproduce:
1. Move the attached file in the lib/docs directory.
2. Open the file.
3. Put the cursor before, e.g., the Additional.lyx include.
4. Press Shift + Down (or Shift + Up).
Result is that there is a small pause before the selection is finished.
Subsequent presses extending the
On 3/11/20 10:24 PM, Scott Kostyshak wrote:
> On Wed, Mar 11, 2020 at 07:56:02PM -0400, Scott Kostyshak wrote:
>> On Wed, Mar 11, 2020 at 10:16:10PM +0100, Jean-Marc Lasgouttes wrote:
>>> Le 11/03/2020 à 21:03, Scott Kostyshak a écrit :
I'm glad I'm not the only one that originally interprette
On Wed, Mar 11, 2020 at 07:56:02PM -0400, Scott Kostyshak wrote:
> On Wed, Mar 11, 2020 at 10:16:10PM +0100, Jean-Marc Lasgouttes wrote:
> > Le 11/03/2020 à 21:03, Scott Kostyshak a écrit :
> > > I'm glad I'm not the only one that originally interpretted JMarc's
> > > comment like that. I made a pa
On Wed, Mar 11, 2020 at 10:16:10PM +0100, Jean-Marc Lasgouttes wrote:
> Le 11/03/2020 à 21:03, Scott Kostyshak a écrit :
> > I'm glad I'm not the only one that originally interpretted JMarc's
> > comment like that. I made a patch thinking he was hinting that I should
> > combine the code to reduce
Le 11/03/2020 à 21:03, Scott Kostyshak a écrit :
I'm glad I'm not the only one that originally interpretted JMarc's
comment like that. I made a patch thinking he was hinting that I should
combine the code to reduce duplication. See attached. Now I realize
that's not what he was trying to say, and
d1e5e60b221
>>>> Author: Scott Kostyshak
>>>> Date: Wed Mar 11 14:18:33 2020 -0400
>>>>
>>>> outline-up/down: preserve cursor's position
>>>> There is no need to change the cursor's position to the
>>>> be
gt; Date: Wed Mar 11 14:18:33 2020 -0400
> >>
> >> outline-up/down: preserve cursor's position
> >> There is no need to change the cursor's position to the
> >> beginning of
> >> the line.
> >> This change
On 3/11/20 3:12 PM, Jean-Marc Lasgouttes wrote:
> Le 11/03/2020 à 19:14, Scott Kostyshak a écrit :
>> commit adb7283b69f5dddfabb8d807a432cd1e5e60b221
>> Author: Scott Kostyshak
>> Date: Wed Mar 11 14:18:33 2020 -0400
>>
>> outline-up/down: preserve cursor
Le 11/03/2020 à 19:14, Scott Kostyshak a écrit :
commit adb7283b69f5dddfabb8d807a432cd1e5e60b221
Author: Scott Kostyshak
Date: Wed Mar 11 14:18:33 2020 -0400
outline-up/down: preserve cursor's position
There is no need to change the cursor's position to the be
On Wed, Mar 11, 2020 at 03:43:00PM +0100, Jean-Marc Lasgouttes wrote:
> Le 10/03/2020 à 15:31, Scott Kostyshak a écrit :
> > Perhaps the following be more reasonable and safer?
> >
> >setCursor(cur, cur.pit(), cur.pos());
> >
> > The above seems safe since I'm just changing "0" to "cur.pos()"
Le 10/03/2020 à 15:31, Scott Kostyshak a écrit :
Perhaps the following be more reasonable and safer?
setCursor(cur, cur.pit(), cur.pos());
The above seems safe since I'm just changing "0" to "cur.pos()", and I
don't see how the length of the paragraph can change after this
operation.
This
ually you are likely right. The destruction of depth structure comes
> with moving paragraphs lfuns, not outlines-up/down.
However, since I'm not sure I suppose I should use the safe version and
put a comment that the line might not be necessary if depth is
guaranteed not to change. Does that sound l
ns, not outlines-up/down.
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Tue, Mar 10, 2020 at 08:55:06AM +0100, Pavel Sanda wrote:
> On Tue, Mar 10, 2020 at 01:24:31AM -0400, Richard Kimberly Heck wrote:
> > On 3/9/20 9:25 PM, Scott Kostyshak wrote:
> > > Is there a reason to do the following for outline-up and outline-down?
> > >
> >
On Tue, Mar 10, 2020 at 01:24:31AM -0400, Richard Kimberly Heck wrote:
> On 3/9/20 9:25 PM, Scott Kostyshak wrote:
> > Is there a reason to do the following for outline-up and outline-down?
> >
> > setCursor(cur, cur.pit(), 0);
> >
> > It does not seem to be
On 3/9/20 9:25 PM, Scott Kostyshak wrote:
> Is there a reason to do the following for outline-up and outline-down?
>
> setCursor(cur, cur.pit(), 0);
>
> It does not seem to be necessary in my testing, but I'm wondering if
> there's a case I'm missing. Or p
Is there a reason to do the following for outline-up and outline-down?
setCursor(cur, cur.pit(), 0);
It does not seem to be necessary in my testing, but I'm wondering if
there's a case I'm missing. Or perhaps it is not necessary but is
desired behavior for some reason?
It ha
un, 2 Feb 2020 16:19:29 -0500
Subject: [PATCH] Paragraph-move-down now moves sub-items as well
---
src/Text3.cpp | 49 +++---
src/support/RandomAccessList.h | 17
2 files changed, 62 insertions(+), 4 deletions(-)
diff --git a/src/Text3.cpp b/s
ituation:
> >
> > 1. One item
> > a. "subitem"
> > 2. Another item
> >
> > Currently (i.e., without the patch), if the cursor is at positiion
> > and the user executes a paragraph-move-down, we get the following:
> >
> > 1.
t;
> Currently (i.e., without the patch), if the cursor is at positiion
> and the user executes a paragraph-move-down, we get the following:
>
> 1. "subitem"
> 2. One item
> 3. Another item
>
> With the patch, the user would get the following:
>
; situation:
> >
> >1. One item
> > a. "subitem"
> >2. Another item
> >
> > Currently (i.e., without the patch), if the cursor is at positiion
> > and the user executes a paragraph-move-down, we get the following:
> >
&g
the patch), if the cursor is at positiion
and the user executes a paragraph-move-down, we get the following:
1. "subitem"
2. One item
3. Another item
With the patch, the user would get the following:
1. Another item
2. One item
a. "subitem"
I
user executes a paragraph-move-down, we get the following:
1. "subitem"
2. One item
3. Another item
With the patch, the user would get the following:
1. Another item
2. One item
a. "subitem"
I believe this functionality would be consistent with the current
beha
On Thu, Apr 18, 2019 at 05:05:30PM +0200, Jean-Marc Lasgouttes wrote:
> Le 18/04/2019 ?? 16:54, Pavel Sanda a écrit :
>> It used to be that LTO could quite increase linking time, is there some
>> visible compil time difference for lyx?
>
> Yes, the link time is longer, but it seems that one can us
Do not redefine a stripped-down LyXRC object.
I am not sure why it was done this way, but it is not really
necessary.
Moreover gcc LTO does not like it.
So it turns out that we can compile with LTO. Is it worth it? Here is what
I get, compared to a release build.
tanuki: size
On Thu, Apr 18, 2019 at 04:42:59PM +0200, Jean-Marc Lasgouttes wrote:
> Le 18/04/2019 ?? 15:49, Jean-Marc Lasgouttes a écrit :
>> commit c6754ed548deecdc37c5a019fb1e5a705dc44da5
>> Author: Jean-Marc Lasgouttes
>> Date: Thu Apr 18 11:53:36 2019 +0200
>> Do not red
Le 18/04/2019 à 15:49, Jean-Marc Lasgouttes a écrit :
commit c6754ed548deecdc37c5a019fb1e5a705dc44da5
Author: Jean-Marc Lasgouttes
Date: Thu Apr 18 11:53:36 2019 +0200
Do not redefine a stripped-down LyXRC object.
I am not sure why it was done this way, but it is not really
On Wed, Jan 31, 2018 at 05:29:38AM +, Joel Kulesza wrote:
> Just came up for me.
Thanks, seems fine here now also.
Scott
signature.asc
Description: PGP signature
Just came up for me.
On Tue, Jan 30, 2018 at 10:23 PM, Scott Kostyshak wrote:
> lyx.org is not responding to me.
>
> Scott
>
lyx.org is not responding to me.
Scott
signature.asc
Description: PGP signature
$ echo $XDG_SESSION_TYPE
x11
On Fri, Jan 5, 2018 at 9:02 AM, LyX Ticket Tracker wrote:
> #10963: long pressing arrow, page up/down delete or backspace does not
> repeat
> action
> ---+-
> Reporter: JohnKarma | Owner: lasgout
5.9.3
Packaging: posix
LyX binary dir: /usr/bin
LyX files dir: /usr/share/lyx
On Wed, Jan 3, 2018 at 10:38 PM, LyX Ticket Tracker wrote:
> #10963: long pressing arrow, page up/down delete or backspace doe
On Tue, Jun 13, 2017 at 07:16:16PM +0200, mn wrote:
> > To be clear, by "consistency", you mean consistency across applications,
> > not consistency within LyX, right?
> >
>
> Right. Across applications and platforms.
> Although, within would entail, if jumping to Pos1 would to enabled, then
>
On 13.06.17 17:26, LyX Ticket Tracker wrote:
> #10701: consistency of cursor behavior for up or down in first or last line
> -+--
> Reporter: Mike | Owner: lasgouttes
> Type: enhancement | Status: new
>
On Fri, May 05, 2017 at 08:21:29AM -0700, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > The following mirror does not work for me:
> >
> > ftp://ftp.u-aizu.ac.jp/pub/tex/lyx/
> >
> > Do we have someone there that we should contact? If this mirror is not
> > up by e.g. beta, should we remove i
On Fri, May 05, 2017 at 08:21:29AM -0700, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > The following mirror does not work for me:
> >
> > ftp://ftp.u-aizu.ac.jp/pub/tex/lyx/
> >
> > Do we have someone there that we should contact? If this mirror is not
> > up by e.g. beta, should we remove i
Scott Kostyshak wrote:
> The following mirror does not work for me:
>
> ftp://ftp.u-aizu.ac.jp/pub/tex/lyx/
>
> Do we have someone there that we should contact? If this mirror is not
> up by e.g. beta, should we remove it from our list of mirrors?
Just kick it out by commenting the offending l
The following mirror does not work for me:
ftp://ftp.u-aizu.ac.jp/pub/tex/lyx/
Do we have someone there that we should contact? If this mirror is not
up by e.g. beta, should we remove it from our list of mirrors?
Scott
signature.asc
Description: PGP signature
I've installed 2.2.2 using installer-3 on a new windows laptop. When I pull
down the menu to select an environment, the font is too small to read, and
the top of each item is cut off. Similarly, in the Preferences menu, under
Look and Feel > Screen Fonts, the samples of the selected f
On Sun, Nov 27, 2016 at 3:54 AM, Christian Ridderström <
christian.ridderst...@gmail.com> wrote:
> On 3 November 2016 at 00:46, Joel Kulesza wrote:
>
>> On Wed, Nov 2, 2016 at 7:25 AM, Jean-Marc Lasgouttes
>> wrote:
>>>
>>> If you are interested in updating this part of the wiki, we can give you
Hi Joel,
On 3 November 2016 at 00:46, Joel Kulesza wrote:
> On Wed, Nov 2, 2016 at 7:25 AM, Jean-Marc Lasgouttes
> wrote:
>>
>> If you are interested in updating this part of the wiki, we can give you
>> the necessary passwords :) Indeed everything is really out of date. The
>> graphical tour s
On Sat, Nov 12, 2016 at 06:51:04PM +0100, Jean-Marc Lasgouttes wrote:
> Le 12/11/2016 à 14:23, Scott Kostyshak a écrit :
> > Hasn't been responding to me for the past 30 minutes or so.
>
> Seems to work right now?
Yes, thanks for checking.
Scott
signature.asc
Description: PGP signature
Le 12/11/2016 à 14:23, Scott Kostyshak a écrit :
Hasn't been responding to me for the past 30 minutes or so.
Seems to work right now?
JMarc
Hasn't been responding to me for the past 30 minutes or so.
Scott
signature.asc
Description: PGP signature
Joel Kulesza wrote:
> http://www.lyx.org/images/about/aqua.png from http://www.lyx.org/Screenshots
If you send me how the mac screen looks nowadays, I can upload it.
If you would like to rework the walk through we will need to give
you access.
Pavel
On Wed, Nov 2, 2016 at 7:25 AM, Jean-Marc Lasgouttes
wrote:
>
> If you are interested in updating this part of the wiki, we can give you
> the necessary passwords :) Indeed everything is really out of date. The
> graphical tour shows proudly LyX 1.3.0pre2!
I might be interested... At the risk of
Le 02/11/2016 à 14:07, Joel Kulesza a écrit :
If you're spending time on infrastructure this weekend, perhaps some
site updates could be included in your work?
http://www.lyx.org/images/about/aqua.png from http://www.lyx.org/Screenshots ;-)
If you are interested in updating this part of the wi
On Tue, Nov 1, 2016 at 7:29 PM, Richard Heck wrote:
>
> I can probably figure this out, but it will be the weekend before I can
> spend the time.
Richard,
If you're spending time on infrastructure this weekend, perhaps some site
updates could be included in your work?
http://www.lyx.org/image
7;t make them go away, but it will keep them from
>> taking us down.
>
> Do you know how to do that? I am not sure that trac is the only
> problem, BTW.
>
> And what is the reasonable limit?
>
> I had some suggestions from Máté: limit the number of connectio
Le 01/11/2016 à 21:06, Jean-Marc Lasgouttes a écrit :
I had some suggestions from Máté: limit the number of connections from the same
IP. IPTables can do this:
http://unix.stackexchange.com/questions/139285/limit-max-connections-per-ip-address-and-new-connections-per-second-with-iptable
Máté
Le 01/11/16 à 21:51, Richard Heck a écrit :
What about rate limiting access to the trac/ subdirectory? The problem
is that we get hit too many times too fast by these bots. Refusing to
serve them that fast won't make them go away, but it will keep them from
taking us down.
Do you know h
em
is that we get hit too many times too fast by these bots. Refusing to
serve them that fast won't make them go away, but it will keep them from
taking us down.
Richard
Le 01/11/2016 à 03:52, Joel Kulesza a écrit :
Does anyone know what the instability is stemming from (hardware,
software, provider, etc.)?
I would say that the problem was receiving the visit of crawl.sogou.com
(220.181.125.68), which sucked 700MiB of data (along with some Amazon
aws guy who
ider, etc.)?
>
>On Mon, Oct 31, 2016 at 5:39 AM, Uwe Stöhr wrote:
>
>> This is now the third down within 2 weeks.
>> We should really start to think about switching our provider.
>>
>> regards Uwe
>>
Paul Johnson wrote:
> Want more mirrors?
Not sure how this helps, if you are normal user and lyx.org does not
work how do you figure out to go to freefaculty.org?
> The big key is that you give me the nearly bonehead proof command to
> run every day.
Full mirror is not possible we run quite more
oblem. If you tell me the "rsync" command to run.
pj
On Mon, Oct 31, 2016 at 9:52 PM, Joel Kulesza wrote:
> Does anyone know what the instability is stemming from (hardware, software,
> provider, etc.)?
>
> On Mon, Oct 31, 2016 at 5:39 AM, Uwe Stöhr wrote:
>>
>&
Does anyone know what the instability is stemming from (hardware, software,
provider, etc.)?
On Mon, Oct 31, 2016 at 5:39 AM, Uwe Stöhr wrote:
> This is now the third down within 2 weeks.
> We should really start to think about switching our provider.
>
> regards Uwe
>
This is now the third down within 2 weeks.
We should really start to think about switching our provider.
regards Uwe
Am 15.10.2016 um 16:27 schrieb Uwe Stöhr:
Am 15.10.2016 um 15:41 schrieb Jean-Marc Lasgouttes:
I restarted it, but I am not sure how long it will stand.
It is again down and we just released a new version.
regards Uwe
Am 15.10.2016 um 15:41 schrieb Jean-Marc Lasgouttes:
I restarted it, but I am not sure how long it will stand.
thanks
regards Uwe
I restarted it, but I am not sure how long it will stand.
JMarc
On Wed, Oct 05, 2016 at 11:47:31AM -0400, Richard Heck wrote:
> On 10/05/2016 10:25 AM, Paul A. Rubin wrote:
> > On 10/05/2016 10:02 AM, Scott Kostyshak wrote:
> >> lyx.org is not responsive for me. This comment also suggests that it's
> >> down for someone else:
&
On 10/05/2016 10:25 AM, Paul A. Rubin wrote:
> On 10/05/2016 10:02 AM, Scott Kostyshak wrote:
>> lyx.org is not responsive for me. This comment also suggests that it's
>> down for someone else:
>> http://tex.stackexchange.com/questions/332712/getting-text-
On 10/05/2016 10:02 AM, Scott Kostyshak wrote:
lyx.org is not responsive for me. This comment also suggests that it's
down for someone else:
http://tex.stackexchange.com/questions/332712/getting-text-to-wrap-in-lyx-table-cells#comment815461_332712
Scott
Confirmed here (and also by Dow
lyx.org is not responsive for me. This comment also suggests that it's
down for someone else:
http://tex.stackexchange.com/questions/332712/getting-text-to-wrap-in-lyx-table-cells#comment815461_332712
Scott
signature.asc
Description: PGP signature
On Thu, Sep 29, 2016 at 07:12:40PM -0700, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > How did you know it was preview_error_? I'm searching for bug-fixing
> > intuition.
>
> valgrind log -> LaTeX.cpp:115 -> clean_start -> buffer.lastPreviewError()
> [Converter.cpp:656] ->
> d->preview_error_
Scott Kostyshak wrote:
> How did you know it was preview_error_? I'm searching for bug-fixing
> intuition.
valgrind log -> LaTeX.cpp:115 -> clean_start -> buffer.lastPreviewError()
[Converter.cpp:656] ->
d->preview_error_ [Buffer.cpp:1200] -> preview_error_ [Buffer.cpp:452] is set
in constructor
On Wed, Sep 28, 2016 at 09:18:37PM -0700, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > I would appreciate it if someone were able to teach me how the steps to
> > take to fix find the root issue.
>
> bunch of variables are not initialized in Buffer::Impl::Impl (unless cloning
> buffer)
> quick
Scott Kostyshak wrote:
> I would appreciate it if someone were able to teach me how the steps to
> take to fix find the root issue.
bunch of variables are not initialized in Buffer::Impl::Impl (unless cloning
buffer)
quick check show these:
layout_position
preview_file_
I am trying to investigate what I think is a bug where sometimes when I
compile sk/Intro.lyx with system fonts + LuaTeX it gives an error and
sometimes not.
I wouldn't be surprised if the Valgrind error I see has nothing to do
with it, but nonetheless it seems important. I get the following error:
Neither Guillaume nor I have received emails regarding the last few
commits.
Scott
signature.asc
Description: PGP signature
This tends to happened when some robot is crawling, I think. We should take a
serious look at the http log at these times if we want to understand what is
going on.
JMarc
Le 12 décembre 2015 08:25:12 GMT+01:00, Georg Baum
a écrit :
>Richard Heck wrote:
>
>> I restarted httpd. Not sure why it
Richard Heck wrote:
> I restarted httpd. Not sure why it was slow this time.
It is slow again:-(
Georg
On 12/11/2015 06:56 PM, Scott Kostyshak wrote:
> On Fri, Dec 11, 2015 at 06:54:43PM -0500, Scott Kostyshak wrote:
>> It was working fine 5 minutes ago but it has not been working the last 5
>> minutes for me. I normally wait a few hours before sending this email,
>> but I've learned that it's good
On Fri, Dec 11, 2015 at 06:54:43PM -0500, Scott Kostyshak wrote:
> It was working fine 5 minutes ago but it has not been working the last 5
> minutes for me. I normally wait a few hours before sending this email,
> but I've learned that it's good to send it early in case someone sees it
> before si
It was working fine 5 minutes ago but it has not been working the last 5
minutes for me. I normally wait a few hours before sending this email,
but I've learned that it's good to send it early in case someone sees it
before signing off for the night.
Scott
signature.asc
Description: PGP signatur
Le 18/10/15 15:31, Georg Baum a écrit :
Jean-Marc Lasgouttes wrote:
I just sent a message to netad...@stw-bonn.de
Seems to have worked ;-)
Yes, these guys are quite responsive.
JMarc
Jean-Marc Lasgouttes wrote:
> I just sent a message to netad...@stw-bonn.de
Seems to have worked ;-)
Georg
Le 18/10/15 01:29, Richard Heck a écrit :
Not sure where to go from there :( I am not sure that we have a live
contact with people of stw-bonn.de who host us.
Lars set that up, didn't he?
I just sent a message to netad...@stw-bonn.de
JMarc
On 10/17/2015 11:14 AM, Jean-Marc Lasgouttes wrote:
Le 17/10/15 16:02, Richard Heck a écrit :
On 10/16/2015 05:11 PM, Jean-Marc Lasgouttes wrote:
Le 16/10/15 18:02, Guillaume Munch a écrit :
Le 16/10/2015 16:57, Scott Kostyshak a écrit :
It has been unresponsive the last half-hour or so.
Sco
Le 17/10/15 16:02, Richard Heck a écrit :
On 10/16/2015 05:11 PM, Jean-Marc Lasgouttes wrote:
Le 16/10/15 18:02, Guillaume Munch a écrit :
Le 16/10/2015 16:57, Scott Kostyshak a écrit :
It has been unresponsive the last half-hour or so.
Scott
Yes, for a few hours here.
Unfortunately, I c
On 10/16/2015 05:11 PM, Jean-Marc Lasgouttes wrote:
Le 16/10/15 18:02, Guillaume Munch a écrit :
Le 16/10/2015 16:57, Scott Kostyshak a écrit :
It has been unresponsive the last half-hour or so.
Scott
Yes, for a few hours here.
Unfortunately, I cannot ssh into the box :( I'll try again to
Le 16/10/15 18:02, Guillaume Munch a écrit :
Le 16/10/2015 16:57, Scott Kostyshak a écrit :
It has been unresponsive the last half-hour or so.
Scott
Yes, for a few hours here.
Unfortunately, I cannot ssh into the box :( I'll try again tomorrow.
JMarc
Le 16/10/2015 16:57, Scott Kostyshak a écrit :
It has been unresponsive the last half-hour or so.
Scott
Yes, for a few hours here.
It has been unresponsive the last half-hour or so.
Scott
I'll have a look ASAP
On Mon, Aug 3, 2015 at 4:51 AM, LyX Ticket Tracker wrote:
> #9708: Cannot step selection back after selecting down out of a multi-line
> inset
> ---+-
> Reporter: skostysh | Owner: lasgouttes
>
It's not for me, or at least not anymore.
A/
On Mon, Dec 29, 2014 at 12:54 PM, Kornel Benko wrote:
>
> Kornel
Kornel
signature.asc
Description: This is a digitally signed message part.
On Fri, Mar 21, 2014 at 9:28 PM, Vincent van Ravesteijn wrote:
> Scott Kostyshak schreef op 22-3-2014 0:49:
>
>> For about 15 minutes now I've been getting
>>
>> 500 Internal Server Error
>>
>> Scott
>
> It seems to be working again.
Same here.
Scott
Scott Kostyshak schreef op 22-3-2014 0:49:
For about 15 minutes now I've been getting
500 Internal Server Error
Scott
It seems to be working again.
Vincent
For about 15 minutes now I've been getting
500 Internal Server Error
Scott
On 12/17/2013 01:03 PM, Georg Baum wrote:
I can't reach trac or use git. Could anybody with enough power have a look
please?
I'll try. There's something weird that happens, though, with way too
many httpd processes being created. This may have to do with trac, but
no one has been able to figu
1 - 100 of 899 matches
Mail list logo
