headers
Neil Hodgson | 1 Nov 11:36
Picon

Re: HTML exporter background color mismatch


Jingcheng Zhang:

> 467c467,471
> <                                                       fprintf(fp, "\tbackground: %s;\n", sd.back.c_str());
> ---
>>                             if (sd.specified & StyleDefinition::sdBack) {
>>                                 fprintf(fp, "\tbackground: %s;\n", sd.back.c_str());
>>                             } else {
>>                                 fprintf(fp, "\tbackground: %s;\n", bgColour.c_str());
>>                             }

   The else branch doesn't appear necessary to me as bgColour is
already the default background colour. Even simpler would be moving
the check for specified into the overall guard:

+++ Exporters.cxx	1 Nov 2009 10:34:10 -0000
@@ -462,7 +462,7 @@
 					} else if (istyle == STYLE_DEFAULT) {
 						fprintf(fp, "\tcolor: #000000;\n");
 					}
-					if (sd.back.length()) {
+					if ((sd.specified & StyleDefinition::sdBack) && sd.back.length()) {
 						if (istyle != STYLE_DEFAULT && bgColour != sd.back) {
 							fprintf(fp, "\tbackground: %s;\n", sd.back.c_str());
 							fprintf(fp, "\ttext-decoration: inherit;\n");

   Neil

--~--~---------~--~----~------------~-------~--~----~
(Continue reading)

Permalink | Reply | 0 comments |
headers
Neil Hodgson | 5 Nov 08:00
Picon

Re: Annoying detection of missing file


mozers:

> OK. But there is another problem.
> SciTE does not notice if the file is removed, moved or renamed by other program.
> That was before. My patch does not change this behavior.
> Attached patch fixes a problem (Author - neo4max)

   I do not understand this code or what it is trying to change.

   One thing it does is that it sets the dirty flag in a way that does
not match the dirty state of the buffer which causes confusion to both
the user and to the code. For example, when it sets the dirty flag
(and thus the '*' in the title bar) you can perform an action and then
undo it and the '*' has gone. If there is a special file-has-gone-away
state then this should be explicit rather than perverting the meaning
of the dirty flag.

   Neil

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 10 comments |
headers
mozers | 6 Nov 11:04
Picon

Re: Annoying detection of missing file

Thursday, November 5, 2009, 10:00:05 AM, Neil wrote:

>    One thing it does is that it sets the dirty flag in a way that does
> not match the dirty state of the buffer which causes confusion to both
> the user and to the code. For example, when it sets the dirty flag
> (and thus the '*' in the title bar) you can perform an action and then
> undo it and the '*' has gone. If there is a special file-has-gone-away
> state then this should be explicit rather than perverting the meaning
> of the dirty flag.

ОК. Please see a new patch (Author - neo4max).
Now creation of the new empty buffer with IDM_OPEN correctly works.

--

-- 
mozers
<http://scite.net.ru>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Attachment (scite.patch): application/octet-stream, 5051 bytes
Permalink | Reply | 0 comments |
headers
neo_max | 6 Nov 12:43
Picon

Re: Annoying detection of missing file


On 5 ноя, 13:00, Neil Hodgson <nyamaton...@gmail.com> wrote:
>    I do not understand this code or what it is trying to change.
>
>    One thing it does is that it sets the dirty flag in a way that does
> not match the dirty state of the buffer which causes confusion to both
> the user and to the code. For example, when it sets the dirty flag
> (and thus the '*' in the title bar) you can perform an action and then
> undo it and the '*' has gone. If there is a special file-has-gone-away
> state then this should be explicit rather than perverting the meaning
> of the dirty flag.

First patch was short version of full modification. In the original
version there is a dialog that asks user to keep deleted file open, it
looks like:

void SciTEBase::CheckReload() {
  if (!props.GetInt("load.on.activate")) return;
  if (filePath.IsUntitled()) return;
  if (CurrentBuffer()->fileMovedAsked) CurrentBuffer()->fileMovedAsked
= CurrentBuffer()->isDirty;
  if ((!CurrentBuffer()->fileMovedAsked)&&(!filePath.Exists())) {
    CurrentBuffer()->fileMovedAsked = true;
    CurrentBuffer()->isDirty = true;
    SString msg = LocaliseMessage(
        "The file '^0' has been deleted, or no longer available. Do
you wish to keep the file open in the editor?",
        filePath.AsFileSystem());
    int decision = WindowMessageBox(wSciTE, msg, MB_YESNO +
MB_DEFBUTTON1);
(Continue reading)

Permalink | Reply | 8 comments |
headers
Sergey Didenko | 8 Nov 10:56
Picon

Re: Clojure-contrib


Emeka, your problem is not related for SCiTe.

":" must be ";" in "java -cp" option on Windows.

On Mon, Aug 31, 2009 at 11:05 AM, Emeka <emekamicro <at> gmail.com> wrote:
> I run on wndows box, I was able to get clojure working but not
> clojure-contrib.
> I have java -cp
> c:\clojure\clojure\cojure.jar:\clojure\clojure-contrib\clojure-contrib.jar
> clojure.lang.Repl
> I will try out ACB.
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 1 comment |
headers
Sergey Didenko | 8 Nov 11:06
Picon

SCiTe for Clojure AKA AnotherClojureBox


Hi Dario,

SciTE for Clojure  AKA ABC cannot be downloaded from
http://www.teradepot.com/qe03ru6ijsqr/ACB1.4.zip.html

What do you think of storing it on google code for example? Then it is
more reliable and is not dependent on some money asking site.

Or may be someone can suggest other places? I could place it on my
hosting for a while, but only if the download count is not big (say <
100 per month)

(see http://sites.google.com/site/dariomac/Home/projects/anotherclojurebox)

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 1 comment |
headers
Neil Hodgson | 9 Nov 02:49
Picon

Re: SCiTe for Clojure AKA AnotherClojureBox


Sergey Didenko:

> What do you think of storing it on google code for example? Then it is
> more reliable and is not dependent on some money asking site.
>
> Or may be someone can suggest other places? I could place it on my
> hosting for a while, but only if the download count is not big (say <
> 100 per month)

   If the code is open source then one of the providers of open source
hosting like Google Code or SourceForge would work. We used to allow
members of scite-interest to upload to the Extras page but spam has
stopped that.

   Neil

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Leledumbo | 9 Nov 06:30
Picon
Favicon

Add support for redirection of standard streams


Right now, if I type in output pane:
<program file> < <input file> > <output file>

where the application reads and writes to standard streams, the
redirection doesn't work and the application still waits for input
from keyboard and outputs the result to output pane.

It would be useful to have redirection supported because we don't need
to open any console first.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 2 comments |
headers
Neil Hodgson | 9 Nov 08:11
Picon

Re: Add support for redirection of standard streams


Leledumbo:

> Right now, if I type in output pane:
> <program file> < <input file> > <output file>

   Use an extra layer of shell. On Windows "cmd /C" and on Linux "sh -c".

   Neil

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 1 comment |
headers
Leledumbo | 9 Nov 11:13
Picon
Favicon

Re: Add support for redirection of standard streams


> Use an extra layer of shell. On Windows "cmd /C" and on Linux "sh -c".

Works as expected, thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |

Gmane