On Sun, Dec 30, 2012 at 5:01 PM, William H. Magill wrote:
> But I don't find anything using textinfo within emacs.
>
Is it MacPorts' emacs, or Apple's? Apple's won't know to look under
/opt/local/share/info for Info files, unless you set INFOPATH in the
environment first or the Elisp equivalent
Does the MacPorts installation of Aspell include Textinfo?
The man page states:
"Aspell is fully documented in its Texinfo manual. See the `aspell' entry in
info
for more complete documentation."
But I don't find anything using textinfo within emacs.
Or is it a separate installation?
On 12/30/2012 08:51 PM, Lawrence Velázquez wrote:
> On Dec 30, 2012, at 8:53 AM, Phil Dobbin wrote:
>
>> A quick how-to would be appreciated, I've never had the need to open one
>> before I don't think.
>
> Wait, really? Color me surprised :P
No, really, it's true :-)
My MBP tells me that I s
On Dec 30, 2012, at 8:53 AM, Phil Dobbin wrote:
> A quick how-to would be appreciated, I've never had the need to open one
> before I don't think.
Wait, really? Color me surprised :P
vq
___
macports-users mailing list
macports-users@lists.macosforge.
On 12/30/2012 05:05 PM, Müller wrote:
> On 2012-12-30 17:51, Phil Dobbin wrote:
>> I'm on Trac at the moment having written up the ticket & can't seem to
>> be able to attach any log files (checked the relevant box but no attach
>> file radio button or indeed any other interface for the job is app
Hi,
I'm wondering if there is a way to select the default pip. It has been
asked here. But I don't see a solution to the problem yet. Thanks!
http://trac.macports.org/ticket/36178
--
Regards,
Peng
___
macports-users mailing list
macports-users@lists.m
On Dec 30, 2012, at 11:16, Federico Beffa wrote:
> after some month I updated my ports and find that the newer version of the
> program "xsane" has a bug and does not close properly (segmentation fault.
> The bug has already been reported).
>
> Now I could in principle revert to the previous
Hi All,
after some month I updated my ports and find that the newer version of the
program "xsane" has a bug and does not close properly (segmentation fault.
The bug has already been reported).
Now I could in principle revert to the previous version. However, the older
version does not run becaus
On 2012-12-30 17:51, Phil Dobbin wrote:
> I'm on Trac at the moment having written up the ticket & can't seem to
> be able to attach any log files (checked the relevant box but no attach
> file radio button or indeed any other interface for the job is apparent).
If you check that checkbox, Trac re
On Dec 30, 2012, at 10:51, Phil Dobbin wrote:
> On 12/30/2012 02:46 PM, Clemens Lang wrote:
>
>> On Sun, Dec 30, 2012 at 02:24:58PM +, Phil Dobbin wrote:
>>> Yeah, looking at 'port installed', I can see the Tcl/Tk upgrade
>>> actually succeeded so why it went ahead & uninstalled Vim & then
On 12/30/2012 02:46 PM, Clemens Lang wrote:
> Hi,
>
> On Sun, Dec 30, 2012 at 02:24:58PM +, Phil Dobbin wrote:
>> Yeah, looking at 'port installed', I can see the Tcl/Tk upgrade
>> actually succeeded so why it went ahead & uninstalled Vim & then
>> re-installed it again, I not sure (Vim's com
On 2012-12-30 15:46, Clemens Lang wrote:
> Oh, I guess the vim binary actually linked against libtcl.dylib, so the
> rebuild was necessary. Vim should be rev-bumped if +tcl is in the
> default variants.
+tcl is not in the default variants of vim, so no action is required.
Rainer
_
Hi,
On Sun, Dec 30, 2012 at 02:24:58PM +, Phil Dobbin wrote:
> Yeah, looking at 'port installed', I can see the Tcl/Tk upgrade
> actually succeeded so why it went ahead & uninstalled Vim & then
> re-installed it again, I not sure (Vim's compile time options were
> +huge +cscope +perl +python27
On Sun, Dec 30, 2012 at 9:08 AM, Clemens Lang wrote:
> > It then proceeded to throw errors on libnewt & expect & uninstalled
> > them & then uninstalled Vim (I had it compiled +tcl) & re-installed
> > Vim without tcl.
>
> So far that's expected to happen; however, it should just have rebuilt
> ex
On 12/30/2012 02:08 PM, Clemens Lang wrote:
> On Sun, Dec 30, 2012 at 01:53:33PM +, Phil Dobbin wrote:
>> I've just ran selfupdate & it stopped at scanning binaries:
>>
>> 'Scanning binaries for linking errors: 9.9%
>> Could not open /opt/local/lib/libtcl8.5.dylib: Error opening or reading
>>
On Sun, Dec 30, 2012 at 01:53:33PM +, Phil Dobbin wrote:
> I've just ran selfupdate & it stopped at scanning binaries:
>
> 'Scanning binaries for linking errors: 9.9%
> Could not open /opt/local/lib/libtcl8.5.dylib: Error opening or reading
> file (referenced from /opt/local/bin/expect)'
So
Hi, all.
I've just ran selfupdate & it stopped at scanning binaries:
'Scanning binaries for linking errors: 9.9%
Could not open /opt/local/lib/libtcl8.5.dylib: Error opening or reading
file (referenced from /opt/local/bin/expect)'
~
It then proceeded to throw errors on libnewt & expect & unins
17 matches
Mail list logo
