Re: nanobits3.patch committed

On Wed, 21 Aug 2002, Jordi Mallach wrote:

> I also upgraded to gettext 0.11.5. Basically, it added a hell lot of m4
> files :)

I'm worried...

Ken.

Re: nanobits3.patch committed

On Tue, Sep 03, 2002 at 08:39:35AM +1000, Ken Tyler wrote:
> > I also upgraded to gettext 0.11.5. Basically, it added a hell lot of m4
> > files :)
> I'm worried...

This one shouldn't cause headaches :)

Jordi
--

-- 
Jordi Mallach Pérez || jordi <at> pusa.informat.uv.es || Rediscovering Freedom,
   aka Oskuro in    || jordi <at> sindominio.net      || Using Debian GNU/Linux
 Reinos de Leyenda  || jordi <at> debian.org          || http://www.debian.org/

http://sindominio.net  GnuPG public information:      pub  1024D/917A225E 
telnet pusa.uv.es 23   73ED 4244 FD43 5886 20AC  2644 2584 94BA 917A 225E

another input_tab() bug, etc.

The bug in input_tab() in the code formerly marked FIXME
also occurs with tab completion of filenames, not just
user names (if started in the middle of the file, they are
tacked onto the end of the string).  I've fixed it so that
the rest of the string is cleared, as my previous fix did.
Since it's a very small fix, I've merged it into
nanoproto.patch, and updated nanoquote31a.patch and
nanopara2.patch accordingly.

In related news, I've gone through all the --enable and
--disable options now with the nanoproto.patch revisions
(separately; I haven't tried every possible combination of
the two yet; I'll do that soon), and everything seems to
be working so far.

http://pooka_regent.tripod.com/patches/nano/nanoproto-patch.txt
http://pooka_regent.tripod.com/patches/nano/nanoquote31a-patch.txt
http://pooka_regent.tripod.com/patches/nano/nanopara2-patch.txt

_____________________________________________________________
Sluggy.Net: The Sluggy Freelance Community!

_____________________________________________________________
Promote your group and strengthen ties to your members with email <at> yourgroup.org by Everyone.net  http://www.everyone.net/?btn=tag

Temporary thaw

Hello all,

	Since I seemed to have a spare five minutes, I finally did some 
useful coding and made the following changes, which breaks my feature 
freeze edict (oh well):

        - Changed do_insertfile to (a) report multibuffer status at the
          prompt and allowing it to be toggled, taking into account the
          need to keep the translatable strings, and (b) added a
          variable inspath to keep track of what the string was before
          toggling.  I'm sure there's bugs, have at it.

I'm tired of being completely clueless about the multibuffer state in my
own text editor.  This way is definitely newbie (and disgruntled
sysadmin) friendly.  Anyway, DLR is going to be commiting the proto
patch soon, so I can't honestly call this release pre-1.2.  Perhaps we
can have a release soon though ;)

Chris A
--

-- 
Chris Allegretta	http://www.asty.org

"Share and Enjoy" - Douglas Adams, 1952 - 2001

Re: another input_tab() bug, etc.

--- David Lawrence Ramsey <pooka_regent <at> sluggy.net> wrote:

<snip>

>In related news, I've gone through all the --enable and
>--disable options now with the nanoproto.patch revisions
>(separately; I haven't tried every possible combination of
>the two yet; I'll do that soon),

"Every possible combination" -> "some possible
combinations."  I obviously can't test absolutely all
combinations of them.

_____________________________________________________________
Sluggy.Net: The Sluggy Freelance Community!

_____________________________________________________________
Promote your group and strengthen ties to your members with email <at> yourgroup.org by Everyone.net  http://www.everyone.net/?btn=tag

(no subject)

Has anyone taken a stab at html or xml syntax highlighting rules for the
default .nanorc?

Mike

p.s. please cc me on any response as I am not subscribed to nano-devel.

Re: Old patch, updated to new CVS.

The patch at http://www.math.cornell.edu/~dbenbenn/nano/ has been updated
again for CVS.

Two comments:

1) Since nano.1.html is automatically generated by man2html, would it make
sense to remove it from CVS (but still keep it in releases)?

2) With an operating directory set, the Insert File prompt is confusing:
"File to insert [from foo]".  The file is actually being inserted from the
current directory.  (Note that Pico does what the prompt suggests: it
reads from the operating directory.)  One fix: remove the [from foo] part. 
If you try to read from outside the OD, you get a warning message saying
what it is anyway.

Re: (no subject)

On Thu, Sep 05, 2002 at 03:15:13PM -0400, Mike Karabinos wrote:
> Has anyone taken a stab at html or xml syntax highlighting rules for the
> default .nanorc?

Not that I know of.
But it'd be great to get a patch! (hint, hint!)

Jordi
--

-- 
Jordi Mallach Pérez || jordi <at> pusa.informat.uv.es || Rediscovering Freedom,
   aka Oskuro in    || jordi <at> sindominio.net      || Using Debian GNU/Linux
 Reinos de Leyenda  || jordi <at> debian.org          || http://www.debian.org/

http://sindominio.net  GnuPG public information:      pub  1024D/917A225E 
telnet pusa.uv.es 23   73ED 4244 FD43 5886 20AC  2644 2584 94BA 917A 225E

Re: Old patch, updated to new CVS.

David Benbennick:
>2) With an operating directory set, the Insert File
>prompt is confusing: "File to insert [from foo]".  The
>file is actually being inserted from the current
>directory.  (Note that Pico does what the prompt
>suggests: it reads from the operating directory.)  One
>fix: remove the [from foo] part.

I'm not seeing this; exactly what directory are you using
as your operating directory, and what are the permissions
on it?  I've tried -o on several of my directories so far;
they all appear to be listed properly on the insert
prompt, and files are inserted properly from them.
(However, in at least one case, nano segfaults on exit
afterward; that appears to be unrelated to this, and I'm
looking into it.)

_____________________________________________________________
Sluggy.Net: The Sluggy Freelance Community!

_____________________________________________________________
Promote your group and strengthen ties to your members with email <at> yourgroup.org by Everyone.net  http://www.everyone.net/?btn=tag

Re: Old patch, updated to new CVS.

On Thu, Sep 05, 2002 at 04:58:00PM -0700, David Lawrence Ramsey wrote:
> I'm not seeing this; exactly what directory are you using
> as your operating directory, and what are the permissions
> on it?

Ah ha!  I have been running nano from a subdirectory of the operating
directory I chose.  At the code handling option 'o' in nano.c:main(), the
check_operating_dir() returns 0 since . is within the operating directory,
so the chdir() doesn't happen.

There is a new patch at http://www.math.cornell.edu/~dbenbenn/nano/ that
fixes this problem and some others.  (operatingdir keyword in the nanorc
didn't chdir(), and an operating directory of / was incorrectly treated
like a non-existant operating dir.)

The attached patch, relative between quote32 and quote33, shows what I
changed, and nearly applies to nano CVS.

diff -u 32/files.c 33/files.c
--- 32/files.c	Thu Sep  5 20:51:49 2002
+++ 33/files.c	Thu Sep  5 20:49:05 2002
 <at>  <at>  -1230,6 +1230,23  <at>  <at> 
 #endif /* !DISABLE_SPELLER */

 #ifndef DISABLE_OPERATINGDIR
+
+/* Initialize full_operating_dir based on operating_dir. */
+void init_operating_dir(void)
+{