Kenichi Handa | 1 Mar 03:53 2006

Re: Printing from modern Emacsen

I'm very sorry for not reponding on this subject.

In article <E1Epoh6-0004iI-Jq <at> fencepost.gnu.org>, "Richard M. Stallman" <rms <at> gnu.org> writes:

> In principle, I think it would be good to move towards a Unicode-based
> printing system for Emacs.  Especially in the Unicode-2 branch.  I am
> not sure how far away we are from that goal.  Handa, can you tell us?

I've been working (but slowly) on using TTF font directly
from ps-print, and just finished the first version of such a
tool (ps-ttf.el; yet another external library for ps-print).
It basically generates a Type42 PostScript font from TTF
(defining only glyphs necessary for printing the current
text) and embed it in the output.

But, it requires a PostScript printer to support TrueType
rasterizer (i.e. version 2013 or the later), and also
requires several backward compatibility issues for version
yanger than 3011.

I tried to address those backward compatibility issues, but
as I don't have an old PostScript printer, I'm not sure how
well it works.

So, I'd like to ask you to print the attached PostScript
file on PostScript printers around you.  As recent
ghostscript has no problem on handling it, if your printer
is drived by ghostscript, you should be able to get the
correct result.

(Continue reading)

Richard Stallman | 1 Mar 18:55 2006
Picon
Picon

Re: c-subword-mode

    Sometimes I get error messages saying that c-subword-mode is a void variable.
    c-subword-mode seems to be a function, so the patch below might be a fix.

That patch seems wrong to me.  If c-subword-mode is defined as a function 
and not as a variable, your patch will CAUSE such an error rather than
prevent it.

Can you provide a Lisp-level backtrace from some occasion where you
get that error?

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Alan Mackenzie | 1 Mar 21:34 2006
Picon

Re: c-subword-mode

Hi, Nick!

On Mon, 27 Feb 2006, Nick Roberts wrote:

>With CC Mode 5.31.3 and GNU Emacs 22.0.50.71 (i686-pc-linux-gnu, X toolkit,
>Xaw3d scroll bars) of 2006-02-25:

>Sometimes I get error messages saying that c-subword-mode is a void variable.
>c-subword-mode seems to be a function, so the patch below might be a fix.

c-subword-mode is normally defined as (define-minor-mode c-subword-mode
....), so it is has both function and variable bindings.  [On older
Emacsen (< 21.1) lacking define-minor-mode, a stub function is defined instead.]

Can you give any more details about how you get a "void variable" error.
It surely cannot be at cc-cmds.el L263.  I don't think the patch is
right.

>-- 
>Nick                                           http://www.inet.net.nz/~nickrob

>*** cc-cmds.el	25 Feb 2006 17:51:43 +1300	1.44
>--- cc-cmds.el	27 Feb 2006 11:43:36 +1300	
>*************** With universal argument, inserts the ana
>*** 259,265 ****
>  		     (if c-hungry-delete-key "h" "")
>  		     (if (and
>  			  ;; cc-subword might not be loaded.
>! 			  (boundp 'c-subword-mode)
>  			  (symbol-value 'c-subword-mode))
(Continue reading)

Nick Roberts | 1 Mar 21:48 2006
Picon

Re: c-subword-mode

 > c-subword-mode is normally defined as (define-minor-mode c-subword-mode
 > ....), so it is has both function and variable bindings.  [On older
 > Emacsen (< 21.1) lacking define-minor-mode, a stub function is defined instead.]

Yes, I misread the code. c-subword-mode just appeared as a function because
it wasn't loaded.

 > Can you give any more details about how you get a "void variable" error.
 > It surely cannot be at cc-cmds.el L263.  I don't think the patch is
 > right.

The patch is surely wrong.  I don't think I've built Emacs correctly.
Sorry for the noise.

--

-- 
Nick                                           http://www.inet.net.nz/~nickrob

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Nick Roberts | 1 Mar 21:39 2006
Picon

Re: c-subword-mode

 >     Sometimes I get error messages saying that c-subword-mode is a void
 >     variable.  c-subword-mode seems to be a function, so the patch below
 >     might be a fix.
 > 
 > That patch seems wrong to me.  If c-subword-mode is defined as a function 
 > and not as a variable, your patch will CAUSE such an error rather than
 > prevent it.

Yes it probably is wrong, but I don't see the point of the test if
c-subword-mode is a function.

 > Can you provide a Lisp-level backtrace from some occasion where you
 > get that error?

If I load a C file, I get:

Debugger entered--Lisp error: (void-variable c-subword-mode)
  c-update-modeline()
  c-basic-common-init(c-mode ((java-mode . "java") (awk-mode . "awk") (other . "gnu")))
  c-common-init(c-mode)
  c-mode()
  set-auto-mode-0(c-mode nil)
  set-auto-mode()
  normal-mode(t)
  after-find-file(nil t)
  find-file-noselect-1(#<buffer myprog.c> "~/myprog.c" nil nil "~/myprog.c" (458851 773))
  find-file-noselect("~/myprog.c" nil nil t)
  find-file("~/myprog.c" t)
  call-interactively(find-file)

(Continue reading)

Chong Yidong | 1 Mar 06:05 2006

Re: Point stuck with adjacent overlays and invisibility spec

(This is based on Ralf Angeli's bug report of Feb 21)

The problem seems to be that adjust_point_for_property fails when we
have invisible text with ellipsis immediately after a 'display string.
I modified Ralf's test case slightly:

  (progn
    (pop-to-buffer (get-buffer-create "*foo*"))
    (erase-buffer)
    (insert "1234567")
    (goto-char (point-min))
    (add-to-invisibility-spec '(outline . t))
    (let ((ov1 (make-overlay 4 5))
          (ov2 (make-overlay 5 6)))
      (overlay-put ov1 'display "xxx"))
      (overlay-put ov2 'invisible 'outline))

This creates a buffer with the contents 1234567, where 4 is overlaid
with the display string "xxx" and 5 is invisible with an ellispis:

123xxx...67

With point on 1, do C-f.  When point reaches 4, I get a Lisp error:

  Debugger entered--Lisp error: (args-out-of-range 5 5)

with no backtrace.  The buffer's redisplay then becomes screwed up.

Everything works as expected if we use '(outline . nil) for the
invisiblity spec, i.e. with no ellipsis.
(Continue reading)

Miles Bader | 1 Mar 07:29 2006
Picon

Re: Printing from modern Emacsen

On 3/1/06, Kenichi Handa <handa <at> m17n.org> wrote:
> As recent
> ghostscript has no problem on handling it, if your printer
> is drived by ghostscript, you should be able to get the
> correct result.

My default printer here at work print this page fine.

However gs version 8.15.1 dies in some gruesome way:

   Unexpected interpreter error -8.
   Error object: (f80)op(0)0x80d9350

[Followed by hex stack dump!]

If I use "gv" (which itself uses gs), it gives a slightly more useful
error message; it says "Warning: Unable to load any usable fontset" on
stderr, and then shows some kind of error page, which says:

  # ERROR: configurationerror
  # OFFENDING COMMAND: setpagedevice

-miles

[i dunno if 8.15.1 is recent, but not too old i think...]

--
Do not taunt Happy Fun Ball.
Kenichi Handa | 1 Mar 08:13 2006

Re: Printing from modern Emacsen

In article <fc339e4a0602282229p1327422cqae5375fff3564131 <at> mail.gmail.com>, "Miles Bader"
<miles <at> gnu.org> writes:

> However gs version 8.15.1 dies in some gruesome way:

>    Unexpected interpreter error -8.
>    Error object: (f80)op(0)0x80d9350

> [Followed by hex stack dump!]

> If I use "gv" (which itself uses gs), it gives a slightly more useful
> error message; it says "Warning: Unable to load any usable fontset" on
> stderr, and then shows some kind of error page, which says:

>   # ERROR: configurationerror
>   # OFFENDING COMMAND: setpagedevice

My gs was much older: GNU Ghostscript 7.05 (2002-04-22).

So, I've just installed the latest version (GPL Ghostscript
8.50 (2005-12-31)), and it prints temp.ps correctly.

Anyway, error on setpagedevice is very strange.  Can you
print some other PS file genenrated by ps-print-buffer with
that ghostscript?

---
Kenichi Handa
handa <at> m17n.org
(Continue reading)

martin rudalics | 1 Mar 14:00 2006
Picon
Picon

Re: Unquoted special characters in regexps

 > Martin Rudalics wrote:
 >
 >    It would be strange to say, for example, that the double-quote
 >    opening an Elisp string is outside the context of the string and
 >    the double-quote that closes it inside.
 >
 > I do not see why you consider this strange.  Quite to the contrary,
 > this is exactly what allows one to determine whether a `"' opens or
 > closes a string.  `"" is special both inside and outside the context
 > of a string.  But its special meaning depends on that context.
 > Outside the context of a string `"' starts a string, inside the
 > context of a string, `"' ends a string.  So an opening `"' is opening
 > _because_ it occurs outside of a string context and the closing `"' is
 > the closing one _because_ it occurs inside a string context.
 >
 > Note that the GNU regexp manual, node `(regex)List Operators' agrees
 > with Andreas and me that `[' is special _outside_ a character alternative
 > (by stating that it is ordinary inside one) and explicitly states that
 > `]' has the special meaning of closing a character alternative
 > _inside_ a character alternative.  (Note that it refers to character
 > alternatives as "lists".)

If you refer to section "3.6 List Operators ([ ... ] and [^ ... ])" of
the GNU regex manual I can exctract three relevant sentences:

"A matching list matches a single character represented by one of the
list items. You form a matching list by enclosing one or more items
within an open-matching-list operator (represented by `[') and a
close-list operator (represented by `]')."

(Continue reading)

Andre Spiegel | 1 Mar 12:43 2006
Picon

Re: complaint: vc-annotate finishes in orig buffer now

On Mon, 2006-02-27 at 05:58 -0500, Thien-Thi Nguyen wrote:

> it used to finish in the annotation buffer,
> which made using P, N and J (browsing commands)
> pleasantly easy.

> this means you have to switch back to the annotation buffer
> to run those commands, which themselves finish outside
> that buffer (since they call `vc-annotate'), the end result
> being constant switching required to browse (not pleasant).

I think this is due to Stefan's change on 2005-12-23 in vc-annotate.  I
think save-current-buffer in the new interactive block of that function
is responsible for it.  Stefan, did you have any particular rationale
for this change?

If not, I would also prefer to revert to the previous behaviour.

> a related complaint is that now vc-annotate creates a new
> window now, whereas before it did not.

Not sure if that is due to the same change.

Gmane