Re: [O] meaning for _ (and perhaps ^) temporalily changed

2019-02-04 Thread Rudolf Sykora
Julius Dittmar writes: > Hi Ruda, > > Am 10.12.18 um 11:32 schrieb Rudolf Sykora: >> is there a way to *temporalily* disable the default interpretation >> of _ as a subscript? >> >> I use filenames which include _ , > > how about enclosing those filenames in a pair of = signs to mark the > fil

Re: [O] meaning for _ (and perhaps ^) temporalily changed

2018-12-12 Thread Kaushal Modi
On Mon, Dec 10, 2018 at 5:34 AM Rudolf Sykora wrote: > > Dear list, > > is there a way to *temporalily* disable the default interpretation > of _ as a subscript? > > I use filenames which include _ , while I have > many other places where I want the default behaviour > (I don't want to rewrite the

Re: [O] meaning for _ (and perhaps ^) temporalily changed

2018-12-10 Thread Julius Dittmar
Hi Ruda, Am 10.12.18 um 11:32 schrieb Rudolf Sykora: > is there a way to *temporalily* disable the default interpretation > of _ as a subscript? > > I use filenames which include _ , how about enclosing those filenames in a pair of = signs to mark the filename itself as text to be passed through

[O] meaning for _ (and perhaps ^) temporalily changed

2018-12-10 Thread Rudolf Sykora
Dear list, is there a way to *temporalily* disable the default interpretation of _ as a subscript? I use filenames which include _ , while I have many other places where I want the default behaviour (I don't want to rewrite these with explicit {} and changing org-use-sub-superscripts variable to