Recent Posts

Pages: 1 [2] 3 4 ... 10
11
SlickEdit® / Re: Why stack trace with nohup doesn't go to my log?
« Last post by patrick on Today at 01:56:14 pm »
When it's a glibc error, it will go out of it's way to write it to the tty rather than let it get redirected.  I've haven't tried it myself, but adding the environment variable "LIBC_FATAL_STDERR_=1" to the environment should force this output to stderr, where it will be redirected as usual.
12
SlickEdit® / Re: Editing Vue files doesn't syntax highlight all file
« Last post by Clark on Today at 12:57:24 am »
We are working on a fix for this.
13
SlickEdit® / Why stack trace with nohup doesn't go to my log?
« Last post by rowbearto on Today at 12:07:41 am »
I normally run SlickEdit on Linux via nohup (from a script) like this:

Code: [Select]
nohup vs >> logfile.log 2>&1 &
So I expect that all stdout and stderr should get saved into logfile.log. I found this trick here: https://unix.stackexchange.com/questions/45913/is-there-a-way-to-redirect-nohup-output-to-a-log-file-other-than-nohup-out

However, occasionally SlickEdit crashes and I see a stack trace printed to the terminal where I launched SE. That happened recently for the issue I wrote about here: https://community.slickedit.com/index.php/topic,16828.0.html

But for the topic of this thread, I would like to know why this stack trace is not in my logfile and instead appears on the terminal where I launched SE?
14
SlickEdit® / Crash - corrupted double-linked list: 0x0000000009cddd70
« Last post by rowbearto on February 19, 2019, 09:58:48 pm »
Got a crash today, but no core dump. However a stack trace was printed to the console. Look for crash_190219.tar.xz on support.

It happened during a build. build_last.log contains the build that occurred on. build_full.log is an accumulation of many recent builds. stack.log has the stack trace.

Using 23.0.1 Linux x64 on CentOs 7.2
15
SlickEdit® / Re: Editing Vue files doesn't syntax highlight all file
« Last post by guth on February 19, 2019, 09:21:22 pm »
I tested this code in a buffer that is 23 lines high. When scrolling so that line 5 becomes top-most, then syntax highlightning disappears. Paste the below Vue code in a buffer that you set as HTML mode.
Code: [Select]
<template>
<h1>hello</h1>
</template>
<script>
export default{
name: "defaultcomp",
props:{
d:{required:true, type:Object}
},
data: function() {
return {
a: "",
b: 0,
c: true
}
},
methods:{
f1: function() {
this.a = "";
},
f2: function() {
this.a = "";
},
f3: function() {
this.a = "";
},
}
}
</script>
16
SlickEdit® / Re: Where is Command Line?
« Last post by Zaphod on February 19, 2019, 08:08:31 pm »
By default, Esc in Brief emulation puts you on the command line. However, this can be changed.

Shouldn't that be "F10" by default?  At least by classic Brief keystrokes and SE 2016 (21.0.x.x).
17
SlickEdit® / Re: Editing Vue files doesn't syntax highlight all file
« Last post by guth on February 19, 2019, 07:22:11 pm »
I see now that when I zoom in a bit in the minimap, there the file is completely syntax highlighted.
18
SlickEdit® / Re: Issue changing indenting from tab to spaces in macro
« Last post by patrick on February 19, 2019, 05:59:00 pm »
No, it's a cheap operation, and there's no harm in it being done twice in a row.
19
SlickEdit® / Re: Issue changing indenting from tab to spaces in macro
« Last post by rowbearto on February 19, 2019, 05:53:39 pm »
Thanks Patrick!

Would it hurt anything if I always kept the " _beautifier_cache_clear(bufId.p_LangId);" in my macro even after you make the hotfix?

Rob
20
SlickEdit® / Re: Editing Vue files doesn't syntax highlight all file
« Last post by Lee on February 19, 2019, 03:00:34 pm »
Do you have a sample you can post?  Will have to do some research and find the spec for .vue to see what differences there are between HTML and VUE.
Pages: 1 [2] 3 4 ... 10