On Thu, Jan 3, 2013 at 5:13 PM, Justin Lebar wrote:
>> Are there any common installations of vi/vim that actually honor
>> modelines anymore? The ones on the Linux distros that I used
>> stopped doing so as a security measure.
Mine (vanilla Ubuntu 12.10) does. I had to |set modelines=2| for it
> Are there any common installations of vi/vim that actually honor
> modelines anymore? The ones on the Linux distros that I used
> stopped doing so as a security measure.
:help modeline says
> No other commands than "set" are supported, for security reasons (somebody
> might create a Trojan hor
On Thursday 2013-01-03 16:44 -0800, Nicholas Nethercote wrote:
> https://developer.mozilla.org/en-US/docs/Developer_Guide/Coding_Style
> says that mozilla code files should have the following Emacs and Vim
> mode lines:
>
> /* -*- Mode: C++; tab-width: 8; indent-tabs-mode: nil;
> c-basic-offset:
On Thursday 2013-01-03 20:02 -0500, Benjamin Smedberg wrote:
> On 1/3/13 7:44 PM, Nicholas Nethercote wrote:
> >Hi
> >
> >https://developer.mozilla.org/en-US/docs/Developer_Guide/Coding_Style
> >says that mozilla code files should have the following Emacs and Vim
> >mode lines:
> >
> > /* -*- Mod
On 1/3/13 7:44 PM, Nicholas Nethercote wrote:
Hi
https://developer.mozilla.org/en-US/docs/Developer_Guide/Coding_Style
says that mozilla code files should have the following Emacs and Vim
mode lines:
/* -*- Mode: C++; tab-width: 8; indent-tabs-mode: nil;
c-basic-offset: 2 -*- */
/* vim: s
Hi
https://developer.mozilla.org/en-US/docs/Developer_Guide/Coding_Style
says that mozilla code files should have the following Emacs and Vim
mode lines:
/* -*- Mode: C++; tab-width: 8; indent-tabs-mode: nil;
c-basic-offset: 2 -*- */
/* vim: set ts=2 et sw=2 tw=80: */
AIUI, |tab-width| in Em
Nathan Froyd wrote:
If you have objections to this change, please speak up, either here or in bug
794178.
set NSPR_LOG_FILE=WinDebug
is currently the only way to get assertions and warnings logged in the
debugger output window. (Other output, such as dump(), is special-cased.)
--
Warning:
Bobby Holley wrote:
In the long term, I'd like for Xray wrappers to behave more logically with
respect to the prototype chain than they have in the past.
Some nodes, such as HTMLImageElement nodes, expose more properties on
their "Xray" wrappers than on their content wrappers. Does this apply
On 2013-01-03 1:28 PM, Benjamin Smedberg wrote:
On 1/3/13 1:23 PM, Boris Zbarsky wrote:
On 1/3/13 1:08 PM, Benjamin Smedberg wrote:
Do we know why this was happening? The log module specifies "nsDebug",
and it should only be written to the log if PR_LOG_MODULES includes
"nsDebug".
It's becaus
On 1/3/13 1:23 PM, Boris Zbarsky wrote:
On 1/3/13 1:08 PM, Benjamin Smedberg wrote:
Do we know why this was happening? The log module specifies "nsDebug",
and it should only be written to the log if PR_LOG_MODULES includes
"nsDebug".
It's because InitLog in nsDebugImpl does this:
gDebugLo
On 1/3/13 1:08 PM, Benjamin Smedberg wrote:
Do we know why this was happening? The log module specifies "nsDebug",
and it should only be written to the log if PR_LOG_MODULES includes
"nsDebug".
It's because InitLog in nsDebugImpl does this:
gDebugLog = PR_NewLogModule("nsDebug");
gDebu
On 1/2/13 9:11 PM, Boris Zbarsky wrote:
On 1/2/13 4:44 PM, Benjamin Smedberg wrote:
Was this particular logging enabled with NSPR_LOG_MODULES=all:5
No.
The failure mode was that if you enabled logging for any module at all
we would crash at shutdown because there was an NS_WARNING after
poi
G'day,
On Wed, Jan 02, 2013 at 10:17:16AM -0800, Jeremy Huddleston Sequoia wrote:
>I haven't been maintaining it for the past few releases because there
>were too many instances of developers continuing to assume that mac ==
>cocoa == bundled app. With every release, there seemed to be more such
13 matches
Mail list logo
